[ http://issues.apache.org/jira/browse/DIRMINA-231?page=comments#action_12425047 ] Brad Harvey commented on DIRMINA-231: -------------------------------------
Hi Niklas, Thanks for all that. My apps that use MINA are still on 0.8.x but they do reuse the socket connectors so they should be ok when we upgrade, and for quickfixj the problem has been resolved by not using a thread pool filter. So I don't have any current problems - I just wanted to make sure the MINA crew were aware of the issue and it sounds like you are :) My only concern is that the default configuration isn't consistent with how you want MINA to be used and is a bit of a trap for beginners. I'd suggest including a warning that using the default config implicitly creates a thread pool for each instance along with your suggestions for proper use in the javadoc and/or tutorial (or is it already there/planned for 1.x?). 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
