Interesting.... we had a similar issue with the MQTT endpoint http://camel.465427.n5.nabble.com/Camel-Endpoint-Consumer-startup-td5757635.html
There the endpoint was also started (causing TCP connections to be established) before any consumers became active (resulting in loss of messages). I'll try to debug this further today -- View this message in context: http://camel.465427.n5.nabble.com/Camel-JMS-message-topic-handling-tp5757853p5757878.html Sent from the Camel - Users mailing list archive at Nabble.com.
