I noted the leak when running a 5.1 SNAPSHOT against JDK 1.5.0_06-b05 for Windows XP Pro SP2.
Joe rajdavies wrote: > > > On 27 Mar 2008, at 04:18, Sachindra Nath wrote: > >> This bug is supposed to have been fixed in SUN VM 1.5.0_12. >> http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=ee6ec97669ab91923bde6c >> d8c041?bug_id=6460501 >> >> Would we still expect the ActiveMQ5.0 + Sun JDK 1.5.0_12 memory leak? > > Possibly - could you use the latest snapshot until we do either a 5.01 > or 5.1 release ? >> >> >> -----Original Message----- >> From: ttmdev [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, March 18, 2008 6:33 PM >> To: users@activemq.apache.org >> Subject: Memory Leak >> >> >> 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. >> > > > -- View this message in context: http://www.nabble.com/Memory-Leak-tp16120738s2354p16396511.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.