[
https://issues.apache.org/jira/browse/DIRMINA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16384868#comment-16384868
]
ASF GitHub Bot commented on DIRMINA-1076:
-----------------------------------------
GitHub user chrjohn opened a pull request:
https://github.com/apache/mina/pull/13
Added tests for issues DIRMINA-1076 and DIRMINA-1077.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chrjohn/mina 2.0
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/mina/pull/13.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #13
----
commit 4f9b2c609aff491702619258babd9ce51dbc1b11
Author: chrjohn <christoph.john@...>
Date: 2018-03-03T21:58:53Z
Added tests for issues DIRMINA-1076 and DIRMINA-1077.
----
> 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
> Components: Core
> Affects Versions: 2.0.16
> Reporter: Christoph John
> Assignee: Jonathan Valliere
> Priority: Major
> Fix For: 2.0.17
>
> 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)
