BTW, once the JVM reaches the out-of-memory condition, it can become impossible to perform any operations on it - such as obtaining stack dumps and heap dumps. With that said, a heap dump, or at least histogram, can help determine the precise cause of the out-of-memory condition.
The jmap program provides one means to obtain heap dumps and histograms. Again, though, it may be unable to do so once the broker JVM runs out of memory, so it may be necessary to run it before hitting that condition in the hopes of capturing the cause earlier. Watching heap usage with jconsole or jvisualvm can also help here to determine if memory is "leaking" (i.e. being consumed and not released more and more over time). -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-hangs-and-i-don-t-understand-why-tp4709963p4709975.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
