Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 27 Sep 2012 01:31:07 +1100 (NCT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <2090793862.128560.1348669868034.JavaMail.jiratomcat@arcas>
In-Reply-To: <1403371983.128537.1348669387521.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (AMQ-4082) Refactor network bridge start/stop to
 reduce async tasks and synchronisation - it is way to complicated atm
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-4082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463854#comment-13463854 ] 

Claus Ibsen commented on AMQ-4082:
----------------------------------

Would it also be possible to do some sort of graceful shutdown (eg as we do in Camel). To allow amble time for inflight messages to complete, and to deny new messages from coming in etc.

                
> Refactor network bridge start/stop to reduce async tasks and synchronisation - it is way to complicated atm
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4082
>                 URL: https://issues.apache.org/jira/browse/AMQ-4082
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>            Reporter: Gary Tully
>             Fix For: 5.8.0
>
>
> sequence of events on a start is way to random as a result of many async tasks.
> It should/could be very simple.
> start remote transport
> wait for remote broker info
> start local transport and local bridge
> start remote bridge
> it is all or nothing w.r.t to success or failure.
> we have sufficient tests in place to safely do the refactor at this stage.
> There have been many bugs in this area and there are still some outstanding
> https://issues.apache.org/jira/browse/AMQ-3993

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira