Try changing the "timeBetweenExpirationCheckMillis" to -1. This will turn off the eviction thread. I don't know what implications this will have for your application so test if there's any impact.
See http://activemq.apache.org/maven/apidocs/org/apache/activemq/pool/PooledConnectionFactory.html On Fri, Feb 7, 2014 at 8:42 PM, Thorsten Höger <li...@hoegernet.de> wrote: > Is there anything to help me on this as I get errors every 30 minutes on > every client > > Thanks > Thorsten > > Am 24.01.2014 15:53, schrieb artnaseef: > > Wish I knew the internals there well enough to solve your problem. > > > > If I had this problem, I would pull down the sources for the Spring DMLC > and > > ActiveMQ connection pools and debug it. My first question is "what logic > > can cause the log message 'The Session is closed'"? > > > > > > > > > > -- > > View this message in context: > http://activemq.2283324.n4.nabble.com/Logentry-Setup-of-JMS-message-listener-invoker-failed-for-destination-tp4676507p4676769.html > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
