You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Jörg Waßmer (JIRA)" <ji...@apache.org> on 2011/03/28 00:17:05 UTC

[jira] [Updated] (AMQ-2662) ActiveMQEndpointWorker.stop() sometimes is needing many minutes to shutdown

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

Jörg Waßmer updated AMQ-2662:
-----------------------------

    Attachment: ActiveMQEndpointWorker.diff

Attached patch for trunk.

> ActiveMQEndpointWorker.stop() sometimes is needing many minutes to shutdown
> ---------------------------------------------------------------------------
>
>                 Key: AMQ-2662
>                 URL: https://issues.apache.org/jira/browse/AMQ-2662
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JCA Container
>    Affects Versions: 5.3.0
>         Environment: irrelevant
>            Reporter: Jörg Waßmer
>             Fix For: 5.5.0
>
>         Attachments: ActiveMQEndpointWorker.diff
>
>
> On shutdowns the threads occasionally are waiting for a long time in ActiveMQEndpointWorker.stop() on the field ActiveMQEndpointWorker.shutdownMutex. The cause is that shutdownMutex is a string constant (initialization line is shutdownMutex = "shutdownMutex"), effectively making it a global lock.
> The hangs are happening especially on servers with high traffic.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira