No, it's 2.7 :) So it looks like the connection is too slow today on my machine and Camel spends too much time to initiate the connection with broker while first sendin(!). My test thinks that it's too late and application doesn't respond and closes everything down. And now the magic happens - there were messages Camel was going to send and while shutting down they it tries to send them again, but ProducerTemplate is stopped already (spring context is shutting down). This is how I see the situation. So what I think is not correct here: 1. Camel tries to initiate connection only when first message comes. I guess this can be cured somehow by configuring Camel in some particular way.. 2. Camel shows 'ProducerTemplate has not been started' instead of 'ProducerTemplate has been stopped'. I deem this is really a misleading behaviour...
-- View this message in context: http://camel.465427.n5.nabble.com/ProducerTemplate-is-not-started-tp4549701p4549867.html Sent from the Camel - Users mailing list archive at Nabble.com.
