Thanks for the quick reply. Yes, the network and the machine load were the prime suspects at first, but then we deployed a second broker with the same config but different ports on the same host, and a test application started opening / closing connections to both of the in parallel every couple of seconds. The slowdown could only be experienced on the broker under load (the second broker had no consumers/producers. It wasn't doing anything except sit there and wait for connections, but a network glitch or a sporadic high load on the server should have affected it as well).
As for the second question, no particular reason except a slip up in design that has been with us for years. -- View this message in context: http://activemq.2283324.n4.nabble.com/Slow-starting-activemq-connection-tp4661562p4661586.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
