[
https://issues.apache.org/jira/browse/APLO-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887063#comment-13887063
]
Hiram Chirino commented on APLO-317:
------------------------------------
Hi AV, is this still occurring?
I've now added -XX:+HeapDumpOnOutOfMemoryError to the default JVM options so
that we can more easily troubleshoot issues like this.
If you get a chance please -XX:+HeapDumpOnOutOfMemoryError to your
configuration and run 'jmap -histo' against the produced memory dump. This
should help us figure out what is using up the memory.
> OutOfMemoryError: unable to create new native thread
> ----------------------------------------------------
>
> Key: APLO-317
> URL: https://issues.apache.org/jira/browse/APLO-317
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker
> Reporter: Vaggelis Atlidakis
>
> Hi,
> We are using in CERN ActiveMQ Apollo and before some months we used to have
> an "OutOfMemoryError". To limit this problem we decided to increase the Heap
> size allocated to JVM. In that spirit, we started running the broker in a fat
> box, featuring 48 GB RAM, and allocated 36 GB to the broker. This temporarily
> solve our problems, but from time to time our broker still gets stuck and we
> manually restart it.
> However, now the logs say: "java.lang.OutOfMemoryError: unable to create new
> native thread".
> After some reading, it seems that the more memory you give to the JVM heap
> the more likely you are to get "java.lang.OutOfMemoryError" unable to create
> new native thread exceptions when you have many threads.
> Clearly, there is somewhere a leak and old threads are not removed.
> Consequently, our broker gets stuck after some days of healthy serving our
> consumers...Any plans of taking care of this bug?
> Best Regards,
> --
> AV
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
