Jason Rosenberg wrote: > > Don't know if you are using connection pooling....I've solved this issue > by setting the idle timeout to 0 (infinite timeout), for pooled > connections.....Unfortunately, the PooledConnectionFactory doesn't expose > the idleTimeout property, so I sub-classed it as a work-around. I've > filed an issue which outlines the work-around: AMQ-1578 >
Interesting reference to this ticket, thank you, Jason I am wondering if this prevents only the warning, so it is more a cosmetical thing. Currently we have instable transactions (cannot save the creation of user account) and we are wondering if activemq could cause that. What is your opinion about that? Ragnar -- View this message in context: http://www.nabble.com/Transport-failed%2C-attempting-to-automatically-reconnect-due-to...-tp15159638s2354p15391508.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
