Hi, sorry, but the issue was a different one. It was my misunderstanding of the idleTimeout property. Is doesn't timeout a connection which is used from the pool, but the connection which the pool opens to the broker. My settings were such that the timeout was too short for the connection pool to cycle through all connections before some of the first connections timed out. So some of the connections from the pool were closed, and of course re-opened when it was their turn again. As soon as the message frequency is higher, or I set the timeout to a higher value, the re-connections to the broker no longer show up in the log file.
Regards, Jochen -- View this message in context: http://activemq.2283324.n4.nabble.com/PooledConnectionFactory-createConnection-results-in-log-entry-Successfully-connected-to-tp4728188p4728324.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
