[ http://issues.apache.org/jira/browse/DIRMINA-231?page=comments#action_12424801 ] Brad Harvey commented on DIRMINA-231: -------------------------------------
Thanks for the background info Niklas. I noticed the problem in an app that was originally using MINA 0.8, so that is probably how the error crept in (see http://www.quickfixj.org/jira/browse/QFJ-34). I guess my concern is that the out of the box behaviour of the connector is for two new threads to be created with no obvious way of shutting them down. Actually, how do you shut them down if using the PooledThreadModel? Thanks, Brad. > 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
