You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Arthur Naseef (JIRA)" <ji...@apache.org> on 2011/06/01 01:30:47 UTC
[jira] [Created] (AMQ-3342) Shutdown of broker waiting for shared
fileystem lock blocks
Shutdown of broker waiting for shared fileystem lock blocks
-----------------------------------------------------------
Key: AMQ-3342
URL: https://issues.apache.org/jira/browse/AMQ-3342
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.4.2
Reporter: Arthur Naseef
Priority: Minor
Shutting down a broker that has not completed startup due to waiting for a shared filesystem lock does not complete.
Using an internal BrokerService() and it's stop() method is definitely impacted.
The attached patch simply adds a check for "isStopped() || isStopping()" to the MessageDatabase lock loop.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-3342) Shutdown of broker waiting for shared
fileystem lock blocks
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-3342.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.6.0
Assignee: Timothy Bish
Created a test case to validate the issue.
Applied patch with some small changes, thanks!
> Shutdown of broker waiting for shared fileystem lock blocks
> -----------------------------------------------------------
>
> Key: AMQ-3342
> URL: https://issues.apache.org/jira/browse/AMQ-3342
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.2
> Reporter: Arthur Naseef
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.6.0
>
> Attachments: amq-3342.patch
>
>
> Shutting down a broker that has not completed startup due to waiting for a shared filesystem lock does not complete.
> Using an internal BrokerService() and it's stop() method is definitely impacted.
> The attached patch simply adds a check for "isStopped() || isStopping()" to the MessageDatabase lock loop.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3342) Shutdown of broker waiting for shared
fileystem lock blocks
Posted by "Arthur Naseef (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arthur Naseef updated AMQ-3342:
-------------------------------
Attachment: amq-3342.patch
Patch which eliminates the blocking.
> Shutdown of broker waiting for shared fileystem lock blocks
> -----------------------------------------------------------
>
> Key: AMQ-3342
> URL: https://issues.apache.org/jira/browse/AMQ-3342
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.2
> Reporter: Arthur Naseef
> Priority: Minor
> Attachments: amq-3342.patch
>
>
> Shutting down a broker that has not completed startup due to waiting for a shared filesystem lock does not complete.
> Using an internal BrokerService() and it's stop() method is definitely impacted.
> The attached patch simply adds a check for "isStopped() || isStopping()" to the MessageDatabase lock loop.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira