OutOfMemory most commonly occurs with slow consumption. The broker can run out of memory if messages are produced to it too quickly and consumers don't keep up. It will also run out of memory if massive transactions are used and not committed nor rolled back before the broker's memory is exhausted.
If this is the cause of problems, changing the JDK used won't eliminate it. A good next diagnostic step is to watch Queues, and Topic subscriptions, for slow consumption and see if that's related to the problem. -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-hangs-and-i-don-t-understand-why-tp4709963p4709974.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
