Keep in mind too that the native thread limit is for the user, counting all processes running as that user on the box, so if you're doing other things on that box as that user you can contribute to this problem. A co-worker ran one of our brokers out of threads after accidentally firing up a couple copies of Eclipse as the ActiveMQ user instead of his own user, so if you did anything like that at the time this happened, that might be the explanation. On Feb 19, 2015 6:44 PM, "artnaseef" <a...@artnaseef.com> wrote:
> Try taking a stack dump of the process once in a while and look at the list > of threads. There may be a leak, such as a connection leak, that needs to > be addressed. Using the stack dump, it should be easy to identify which > threads are being created and sticking around for a long time. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/java-lang-OutOfMemoryError-in-consumer-application-tp4691751p4691790.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
