If you're running ActiveMQ on a 1.5 VM, you may have noticed a very slow and steady memory leak with the broker even when it is sitting idle.
The leak, which is in the VM and not the broker, has been addressed in the 1.6 VM. The culprit is the java.util.concurrent package, and relative to ActiveMQ it is the use of the java.util.concurrent.LinkedBlockingQueue.poll() method call w/in the TcpTransport class. You can view the documentation for this bug in the Java bug database. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6491621 Joe Goto www.ttmsolutions.com for a free ActiveMQ user guide -- View this message in context: http://www.nabble.com/Memory-Leak-tp16120738s2354p16120738.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
