Hi,
It checked it and it was because of the client application was running more
processes then the ulimit configured.
Thanks,
Anuj
--
View this message in context:
http://activemq.2283324.n4.nabble.com/java-lang-OutOfMemoryError-in-consumer-application-tp4691751p4691810.html
Sent from the Act
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 coupl
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 t
This is caused by hitting the native thread limit for the user that
ActiveMQ runs as, causing the JVM to be "unable to create a new native
thread" as stated in the stack trace you quoted. Increase that user's
maxproc setting in the Linux OS (I assume you're running Linux, since I
don't think this
