You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2007/10/19 12:32:50 UTC

[jira] Created: (QPID-654) ThreadPoolExecutor.getTask() can be seen WAITING causing test cases to hang

ThreadPoolExecutor.getTask() can be seen WAITING causing test cases to hang
---------------------------------------------------------------------------

                 Key: QPID-654
                 URL: https://issues.apache.org/jira/browse/QPID-654
             Project: Qpid
          Issue Type: Bug
          Components: Java Client
    Affects Versions: M2, M2.1
            Reporter: Martin Ritchie
            Assignee: Martin Ritchie


This occured in the LargeMessageTest. Not entirely sure why as there is a connection.close() call and that does call _taskpool.shutdown() which in turn will interupt the worker threads that are WAITING in getTask(). 

In either case there may be occasions when there are worker threads processing and we may wish to stop them also. Adding a shutdownNow() would be advisable.

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


[jira] Resolved: (QPID-654) ThreadPoolExecutor.getTask() can be seen WAITING causing test cases to hang

Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Godfrey resolved QPID-654.
------------------------------

       Resolution: Fixed
    Fix Version/s: M2.1

> ThreadPoolExecutor.getTask() can be seen WAITING causing test cases to hang
> ---------------------------------------------------------------------------
>
>                 Key: QPID-654
>                 URL: https://issues.apache.org/jira/browse/QPID-654
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M2, M2.1
>            Reporter: Martin Ritchie
>            Assignee: Martin Ritchie
>             Fix For: M2.1
>
>
> This occured in the LargeMessageTest. Not entirely sure why as there is a connection.close() call and that does call _taskpool.shutdown() which in turn will interupt the worker threads that are WAITING in getTask(). 
> In either case there may be occasions when there are worker threads processing and we may wish to stop them also. Adding a shutdownNow() would be advisable.

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