Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <10991062.1173112083022.JavaMail.jira@brutus>
Date: Mon, 5 Mar 2007 08:28:03 -0800 (PST)
From: "Jonas Lim (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQ-1181) Avoid Network Deadlocks if possible
In-Reply-To: <32708417.1172519042814.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

Jonas Lim resolved AMQ-1181.
----------------------------

    Resolution: Fixed

ported to trunk : r514720

> 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.