we were seeing similar issues and tracked it back to and ActiveMQConnectionPool idleTimeout issue: https://issues.apache.org/jira/browse/AMQ-4366
the solution for us was to explicitly set the idleTimeout to 0 to disable this ActiveMQMessageConsumer.checkClosed() logic... indrayani wrote > Hi , > I understood that these are just warnings , > but what could be the reason behind getting consumer closed and session > closed warnings. > if you check the scenario that i have mentioned , then in that case , 2 > web applications are communicating with each other via camel routes which > consist of servlet and actimq endpoints, > now in this case , neither of the web application is down, but still after > first 2 request-reply , i am getting consumer closed exception for one of > the activemq and session closed exception for the other activemq. > > I am just curious, why am i not getting the exceptions in the first 2 > communictions and why for 3rd ? > > it would be really helpful if you elaborate more on this. ----- Ben O'Day IT Consultant -http://consulting-notes.com -- View this message in context: http://camel.465427.n5.nabble.com/Activemq-consumer-is-closing-tp5731140p5734449.html Sent from the Camel - Users mailing list archive at Nabble.com.
