[ http://issues.apache.org/jira/browse/DIRMINA-231?page=comments#action_12424889 ] Niklas Therning commented on DIRMINA-231: -----------------------------------------
Actually, I was wrong about the waitForItem() method. The way the LeaderFollowersThreadPool (used by default) works is that there is always at least one thread (the leader) alive. The keepAliveTime doesn't apply to this thread so destroy() must be called to kill it. > SocketConnector thread leak > --------------------------- > > Key: DIRMINA-231 > URL: http://issues.apache.org/jira/browse/DIRMINA-231 > Project: Directory MINA > Issue Type: Bug > Affects Versions: 0.9.5 > Environment: jdk1.5.0_06 > Reporter: Brad Harvey > Assigned To: Niklas Therning > Priority: Critical > Attachments: ConnectionTest.java, ConnectionTest.java > > > A few new threads are created for new SocketConnectors when they attempt to > connect to a remote host. Two of these (AnonymousIoService-x-y) are not > cleaned up which can eventually lead to OutOfMemoryError or other strange > behaviour. > It can be avoided by reusing SocketConnectors, but I don't think this should > be necessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
