Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 82460 invoked from network); 26 Feb 2007 19:44:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Feb 2007 19:44:31 -0000 Received: (qmail 76959 invoked by uid 500); 26 Feb 2007 19:44:32 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 76944 invoked by uid 500); 26 Feb 2007 19:44:32 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 76931 invoked by uid 99); 26 Feb 2007 19:44:32 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Feb 2007 11:44:32 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Feb 2007 11:44:23 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CB79F71403A for ; Mon, 26 Feb 2007 11:44:02 -0800 (PST) Message-ID: <32708417.1172519042814.JavaMail.jira@brutus> Date: Mon, 26 Feb 2007 11:44:02 -0800 (PST) From: "Hiram Chirino (JIRA)" To: dev@activemq.apache.org Subject: [jira] Created: (AMQ-1181) Avoid Network Deadlocks if possible MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org 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.1, 4.0 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.