You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2007/02/26 20:15:02 UTC
[jira] Created: (AMQ-1179) Broker Connection Shutdown is prone to
lockup/deadlock
Broker Connection Shutdown is prone to lockup/deadlock
------------------------------------------------------
Key: AMQ-1179
URL: https://issues.apache.org/activemq/browse/AMQ-1179
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.1.0, 4.0.2, 4.0.1, 4.0
Reporter: Hiram Chirino
Assigned To: Hiram Chirino
Fix For: 4.1.1, 4.2.0
There are several scenarios (timing related) where the broker does not properly shutdown it's connections to a client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1179) Broker Connection Shutdown is prone to
lockup/deadlock
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38597 ]
Hiram Chirino commented on AMQ-1179:
------------------------------------
Several fixes were recently done in the 4.1 branch to make connection shutdown more robust:
Send the ShutdownInfo message in a async thread so that the operation can timeout if the connection fails while doing that:
http://svn.apache.org/viewvc?view=rev&rev=511090
http://svn.apache.org/viewvc?view=rev&rev=511091
http://svn.apache.org/viewvc?view=rev&rev=511089
http://svn.apache.org/viewvc?view=rev&rev=511083
> Broker Connection Shutdown is prone to lockup/deadlock
> ------------------------------------------------------
>
> Key: AMQ-1179
> URL: https://issues.apache.org/activemq/browse/AMQ-1179
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 4.0, 4.0.1, 4.0.2, 4.1.0
> Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.1.1, 4.2.0
>
>
> There are several scenarios (timing related) where the broker does not properly shutdown it's connections to a client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1179) Broker Connection Shutdown is prone to
lockup/deadlock
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38599 ]
Hiram Chirino commented on AMQ-1179:
------------------------------------
Need to port all the previously posted revisions to trunk.
> Broker Connection Shutdown is prone to lockup/deadlock
> ------------------------------------------------------
>
> Key: AMQ-1179
> URL: https://issues.apache.org/activemq/browse/AMQ-1179
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 4.0, 4.0.1, 4.0.2, 4.1.0
> Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.1.1, 4.2.0
>
>
> There are several scenarios (timing related) where the broker does not properly shutdown it's connections to a client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1179) Broker Connection Shutdown is prone to
lockup/deadlock
Posted by "Jonas Lim (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonas Lim resolved AMQ-1179.
----------------------------
Resolution: Fixed
ported fix to trunk : r514734
> Broker Connection Shutdown is prone to lockup/deadlock
> ------------------------------------------------------
>
> Key: AMQ-1179
> URL: https://issues.apache.org/activemq/browse/AMQ-1179
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 4.0, 4.0.1, 4.0.2, 4.1.0
> Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.1.1, 4.2.0
>
>
> There are several scenarios (timing related) where the broker does not properly shutdown it's connections to a client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.