mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Valliere (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRMINA-1076) Leaking NioProcessors/NioSocketConnectors hanging in call to dispose
Date Fri, 09 Feb 2018 14:58:00 GMT

    [ https://issues.apache.org/jira/browse/DIRMINA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358497#comment-16358497
] 

Jonathan Valliere commented on DIRMINA-1076:
--------------------------------------------

What is the JDK version?  What Ubuntu version?

What CPU governor are you using on Ubuntu on your i5-2410M?  You can install 'indicator-cpufreq'
([https://apps.ubuntu.com/cat/applications/quantal/indicator-cpufreq/)] which allows you
to change your CPU frequency governor. If available, set it to your CPU max (non-turbo) frequency
and run the test again; otherwise set to "Performance" and run the test again.  Because you
are using a mobile chipset, I would like to make sure that the frequency scaler on your platform
isn't a contributing factor allowing deadlocks to happen more often.

My goal is to get my environment to deadlock quickly and often; just like yours.

I'm going to set this up for tomorrow.  If I can't get the results I want on my desktop,
I'll setup a 2 core VM to try it from.

> 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
>            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)

Mime
View raw message