activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1181) Avoid Network Deadlocks if possible
Date Mon, 26 Feb 2007 19:57:02 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38601
] 

Hiram Chirino commented on AMQ-1181:
------------------------------------

Several changes went into the 4.1 branch to help avoid these network deadlocks:

http://svn.apache.org/viewvc?view=rev&rev=511085 - enabled flow control again on network
producers, but now use the sync acking on queues to avoid blocking the network connection.
 Takes advantage of the fix to AMQ-1123 solve deadlocks at the network bridge.
http://svn.apache.org/viewvc?view=rev&rev=511080 - disabled flow control on network producers

> Avoid Network Deadlocks if possible
> -----------------------------------
>
>                 Key: AMQ-1181
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1181
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 4.0, 4.0.1
>            Reporter: Hiram Chirino
>         Assigned To: Hiram Chirino
>             Fix For: 4.1.1, 4.2.0
>
>
> When you depend on the brokers to flow control your producers, the brokers are usually
running with usage managers at 100%.  Now if use this in network of brokers configuration
it is very easy to get into a scenario where the brokers network bridges lock messages to
send to the next broker but bock on the send and thus create a network deadlock.

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


Mime
View raw message