Brokers were slow at the time. Jvm max heap is set at 2048MB, starting the brokers clean memory usage usually starts from 200MB and slowly starts rising as more threads are being used. Usual thread usage will go up to about 300-400 on brokers together. Right now broker b is running 246 threads and using 400-500MB and broker a 132 threads and 600-900MB. Gradually memory usage increases with both brokers over time (could be a memory leak?). When the slowdown becomes noticeable jvm is not even pushing close to its heap limit. The producer consumer topology is difficult to explain. We're using an application that itself uses activemq as a backbone to relay messages to both internal components and external client application parts.
-- View this message in context: http://activemq.2283324.n4.nabble.com/Connecting-to-broker-slows-down-tp4667017p4667070.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
