Menu
  • HOME
  • TAGS

Error running quickstart-camelservlet in OpenShift V3 with Fabric8 and Docker

docker,openshift,fabric8

Looks like version 2.0.30 of fabric8 does not accept the default namespace which is a empty string. You should try a previous version of the plugin. I have tried with 2.0.25 and looks like it is working.

Failed to deploy quickstart to Fabric8 on Jube

java,maven,apache-camel,jbossfuse,fabric8

Unfortunately with recent bigger changes to upgrading to kubernetes v1beta3 apis, and changes on the web console to use web sockets and we are in process of upgrading jube to use hawtio v2 as the web console, so it uses exactly the same web console as you would on a...

Apache Camel, DirectConsumerNotAvailableException while runing cxf on fabric8(karaf), though local runs fine

cxf,apache-camel,karaf,fabric8

Looking at your code at GitHub, I don't see any direct://smsinfo consumer endpoint, thus the Camel error seems to be adequate. So, I guess, that your local setup is different from the one at your fabric8 instance. By the way, I tried to build your GitHub project, but failed with...

How to use dependent bundles in different container in Fabri8?

osgi,jboss6.x,jbossfuse,karaf,fabric8

No this is not possible. Package export and import on OSGi level is bounded to the JVM. This means bundles in different JVMs will not be able to import each others classes. The only OSGi concept that supports clustering are Services. The OSGi specification calls that Remote Services. See: https://wiki.eclipse.org/Tutorial:_Building_your_first_OSGi_Remote_Service...

Camel/ActiveMQ Transactions, Redelivery and DLQs

java,apache-camel,activemq,fabric8

You should configure the redelivery options on the AMQ broker as when you use TX, its the brokers responsible for doing the redelivery (not Camel).

Best way to load dynamically routes in Apache Camel

osgi,apache-camel,dsl,jbossfuse,fabric8

I think a good approach is to group your routes into small contexts with just a few (or maybe even single) routes per context. Then you reload that small context without causing interruption in other routes. However, as you don't believe in that approach, you can easily add and remove...