So if I run my very simple app that listens to the topic 10 times, 9 times camel just doesn’t receive messages. I’m looking at the log in DEBUG mode and the difference I’ve noticed is that when it does start normally there are lines like this: 2011-03-24 14:55:38,838[][INFO ][main ][nection.CachingConnectionFactory] - Established shared JMS Connection: com.solacesystems.jms.SolConnection@72bcaa 2011-03-24 14:55:38,838[][DEBUG][main ][.jms.JmsMessageListenerContainer] - Established shared JMS Connection 2011-03-24 14:55:38,838[][DEBUG][main ][.jms.JmsMessageListenerContainer] - Resumed paused task: org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker@1813c20
In cases when it doesn’t start normally, I can see only this line: 2011-03-24 12:02:00,229[][INFO ][main ][nection.CachingConnectionFactory] - Established shared JMS Connection: com.solacesystems.jms.SolConnection@1127169 I don’t know where the issue is, but the fact that in first log you can see JmsMessageListenerContainer log makes me think that it’s not loaded during failure startup. And the fact that it doesn’t occur all the time makes me think that it happens because of concurrency. We use Camel 2.7.0 and Solace with its JMS implementation if it's important. Can someone help me out with this issue? Best Regards, Stanislav Bashkirtsev -- View this message in context: http://camel.465427.n5.nabble.com/Camel-doesn-t-listen-to-JMS-channel-tp4263097p4263097.html Sent from the Camel - Users mailing list archive at Nabble.com.
