Hi Okay fixed by https://issues.apache.org/jira/browse/CAMEL-9899
Its because you stop the jms consumer from the event thread which is the thread that consumed the message. The ticket resolves this by stopping using a thread pool for those tasks so they dont steal the thread from RX. On Thu, Apr 21, 2016 at 6:42 PM, arunkabraham <arunk2...@gmail.com> wrote: > I have created a sample project and uploaded the zip to the github location > https://github.com/arunkabraham/Camel-RX > <https://github.com/arunkabraham/Camel-RX> > > Its just a main program which sends a messages to activemq and fetch it from > there using camel-RX. > But the connection to the active-mq is live after receiving and calling > oncomplete. > > I wanted to get this connection closed. > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-rx-is-not-releasing-the-ActiveMQ-connection-once-the-subscription-is-complete-tp5781482p5781492.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
