Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 1 Jul 2011 17:38:28 +0000 (UTC)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1392519978.9111.1309541908991.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (AMQ-2324) Forwarded message cannot be
 distributed to the original broker
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Gary Tully reassigned AMQ-2324:
-------------------------------

    Assignee: Gary Tully  (was: Bruce Snyder)

> Forwarded message cannot be distributed to the original broker
> --------------------------------------------------------------
>
>                 Key: AMQ-2324
>                 URL: https://issues.apache.org/jira/browse/AMQ-2324
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.2.0
>            Reporter: ying
>            Assignee: Gary Tully
>             Fix For: 5.6.0
>
>
> I have a simple cause which can cause dispatch problem:
> 1. setup a network of broker1, broker2, bridged by multicast discovery
> 2. make a producer send 5 msg to queueA to broker2
> 3. make a consumer to consume from broker1 queueA ( make it slow, so it only consumer 1 msg) but make sure all 5 msg from broker2 are forwared to broker1
> 4. stop the consumer to broke1, restart it to consume from broker2 queueA
> 5. the 4 msgs originally published to broker2 and forwarded to broker1 and has not yet been consumed will stuck on broker1 and will not forwarded to broker2 for the consumer to consume. 
> Here is an solution: it checks forwarded to broker( eg, broker1) to see whether it has any active consumer, it will be able forward the message back to the original broker when there is no active consumer on the forwarded to broker.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira