You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Arnaud Simon (JIRA)" <qp...@incubator.apache.org> on 2008/04/18 15:22:21 UTC

[jira] Resolved: (QPID-928) Test org.apache.qpid.test.unit.client.connection.ConnectionCloseTest intermittently failing

     [ https://issues.apache.org/jira/browse/QPID-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arnaud Simon resolved QPID-928.
-------------------------------

    Resolution: Fixed

r648661

> Test org.apache.qpid.test.unit.client.connection.ConnectionCloseTest intermittently failing 
> --------------------------------------------------------------------------------------------
>
>                 Key: QPID-928
>                 URL: https://issues.apache.org/jira/browse/QPID-928
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Tests
>    Affects Versions: M3
>            Reporter: Arnaud Simon
>             Fix For: M3
>
>
> This test is failing because more than 10 threads are still running immediately after the 500 connections are closed. It appears that those threads are Mina threads waiting on a selector key. Those threads are eventually notified if the main thread waits before checking for potential spurious threads. 
> As the threshold (currently set to 10) is arbitrary, I would suggest that we wait 1s before making the check that should leave all type of hardware enough time to cleanup, we would then use a 0 threshold i.e. no spurious thread would be tolerated.
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.