Any time you get an OutOfMemory exception, that means memory for the JVM has been exhausted, and will lead to all kinds of failed processing. Even getting an OutOfMemory exception logged anywhere can be tricky since the logging may need to allocate memory.
Look for leaks in the client. A good too here is jconsole, or visualvm, to watch the heap size. JMap or visualvm will grab a heap dump that can later be analyzed to determine what objects are using up the majority of heap space. Get that solved, and I suspect your problems will go away. -- View this message in context: http://activemq.2283324.n4.nabble.com/producer-is-getting-stuck-tp4676567p4676616.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
