Is this problem related to recipientList? Or it is general issue with camel request/reply over jms? I haven't noticed this behaviour in other routes with InOut pattern over amq queue. Do you have any link to jira issue or other pages where this problem is described?
Thank you. -- View this message in context: http://camel.465427.n5.nabble.com/Lots-of-ActiveMQMessageConsumer-with-selector-JMSCorrelationID-CamelDummyJmsMessageSelector-tp5736921p5736927.html Sent from the Camel - Users mailing list archive at Nabble.com.
