You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/05/04 15:36:01 UTC
[jira] [Work logged] (DIRMINA-1076) Leaking
NioProcessors/NioSocketConnectors hanging in call to dispose
[ https://issues.apache.org/jira/browse/DIRMINA-1076?focusedWorklogId=237216&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-237216 ]
ASF GitHub Bot logged work on DIRMINA-1076:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/May/19 15:35
Start Date: 04/May/19 15:35
Worklog Time Spent: 10m
Work Description: asfgit commented on pull request #13: Added tests for issues DIRMINA-1076 and DIRMINA-1077.
URL: https://github.com/apache/mina/pull/13
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 237216)
Time Spent: 10m
Remaining Estimate: 0h
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)