[ https://issues.apache.org/jira/browse/DIRMINA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16375929#comment-16375929 ]
Jonathan Valliere commented on DIRMINA-1076: -------------------------------------------- {{selector.close()}} occurs inside of the {{IoProcessor}} worker thread. And it only happens when the event loop exits (unless called directly through a non public function), therefore, the number of keys must be 0 before {{IoProcessor}} will call {{selector.close()}}. The extra {{select()}} loop is to cause the {{selector}} to update {{selector.keys().size()}}. I think its fine the way it is. If it concerns you, we can change the loop timeout to something smaller, like 250ms. > Leaking NioProcessors/NioSocketConnectors hanging in call to dispose > -------------------------------------------------------------------- > > Key: DIRMINA-1076 > URL: https://issues.apache.org/jira/browse/DIRMINA-1076 > Project: MINA > Issue Type: Bug > Affects Versions: 2.0.16 > Reporter: Christoph John > Assignee: Jonathan Valliere > Priority: Major > Attachments: mina-dispose-hang.txt, mina-test-log.txt, > mina-test-patch.txt > > > Follow-up to mailing list discussion. > I was now able to reproduce the problem with a MINA test. Or let's say I did > the brute-force approach by re-running one test in an endless loop. > I have attached a patch of AbstractIoServiceTest (against > [https://github.com/apache/mina/tree/2.0]) and a stack trace. After a few > loops the test is stuck. You can see a lot of threads hanging in dispose() > and the test is stuck when it tries to dispose the acceptor. > > What is a little strange is that the javadoc says that > connector.dispose(TRUE) should not be called from an IoFutureListener, but in > the test it is done anyway. However, changing the parameter to FALSE does not > help either. > > Is there anything that can be done to prevent this hang? -- This message was sent by Atlassian JIRA (v7.6.3#76005)