That's great news. Sorry for never responding to your last two emails; I still had them flagged to come back to, but nothing in the thread dump gave me any idea of what was going on. Now that you've determined that the behavior was driven by external forces rather than something within the broker, that makes complete sense.
Tim On Aug 1, 2017 3:57 AM, "Siebo" <blacktora...@gmail.com> wrote: > Hi, > > Finally, my problem was solved. It was a mistake from load balance tool > which made continuous command call to check activemq alive or not. By some > reasons, it made the number of thread increase by time and activemq die > when > it exceeded maximum threads. > Thank you all (especially Tim) did help me a lot in resolving this trouble. > > Thanks and best regards, > Siebo > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/org-apache-activemq-broker-TransportConnection-Transport- > Transport-Connection-to-tcp-XX-XX-XXX-XXX-5n-tp4722840p4729102.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
