Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-dev@geronimo.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <31424676.1142596226055.JavaMail.tomcat@stilton>
Date: Fri, 17 Mar 2006 03:50:26 -0800 (PST)
From: "james strachan (JIRA)" <jira@activemq.org>
To: activemq-dev@geronimo.apache.org
Subject: [jira] Resolved: (AMQ-588) Broker shutdown no longer works in 02/21
 SNAPSHOT, when using static+failover NetworkConnectors.
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ http://jira.activemq.org/jira//browse/AMQ-588?page=all ]
     
james strachan resolved AMQ-588:
--------------------------------

    Resolution: Fixed

Good catch; the static: and failover: are quite similar really and one or the other should be used. I've tried to fix the documentation to make this absolutely clear...

http://docs.codehaus.org/display/ACTIVEMQ/Networks+of+Brokers

in particular I've added your issue as a big read warning on that page so hopefully others won't make the same mistake :)

> Broker shutdown no longer works in 02/21 SNAPSHOT, when using static+failover NetworkConnectors.
> ------------------------------------------------------------------------------------------------
>
>          Key: AMQ-588
>          URL: http://jira.activemq.org/jira//browse/AMQ-588
>      Project: ActiveMQ
>         Type: Bug

>   Components: Broker
>     Versions: 4.0
>  Environment: JDK 1.5.0_04, Solaris 8 / Solaris 10
>     Reporter: Kevin Yaussy
>      Fix For: 4.0 M5

>
>
> When using a static+failover list for network connections, Broker shutdown is no longer working as of the 02/21/2006 SNAPSHOT release.  If a broker is attempting to connect to another broker which is not currently running, the shutdown blocks waiting for the failover connect thread to complete the connection.  Since the other broker is not running, the shutdown then hangs.
> This scenario worked fine with the 02/17/2006 SNAPSHOT release.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira