JMX shows failed Camel contexts that are invisible to OSGi/Karaf

1. In a clean installation of Fuse 6.3, install the feature camel-http. 2. Copy this Blueprint XML to a file in the deploy/ directory <?xml version= "1.0" encoding= "UTF-8" ?> <blueprint xmlns= "http: //www.osgi.org/xmlns/blueprint/v1.0.0" xmlns:xsi= "http: //www.w3.org/2001/XMLSchema-instance" xmlns:cxf= "http://camel.apache.org/schema/blueprint/cxf" xmlns:cm= "http: //aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0" xsi:schemaLocation="http: //www.osgi.org/xmlns/blueprint/v1.0.0 http: //www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd"> <camelContext xmlns= "http: //camel.apache.org/schema/blueprint" streamCache= " true " > <route id= "test" > <!--from uri= "timer: //foo?period=1000&amp;fixedRate= true " /--> <from uri= "http: //localhost:6000/" /> <setBody><simple>Hello</simple></setBody> <to uri= "log: //foo" /> </route> </camelContext> </blueprint> It fails to initialize because "http" cannot be a consumer endpoint. 3. Note that "context-list" shows no Camel contexts, but JMX (e.g., jconsole) shows an entry for "camel-context-1" that is difficult to distinguish from a viable context that happens to be stopped.