Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-dev@geronimo.apache.org
Message-ID: <1826112.1146038987788.JavaMail.root@brutus>
Date: Wed, 26 Apr 2006 08:09:47 +0000 (GMT+00:00)
From: "Kieran Murphy (JIRA)" <jira@apache.org>
To: activemq-dev@geronimo.apache.org
Subject: [jira] Reopened: (AMQ-630) After broker has shutdown, cannot
 shutdown a client application
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ https://issues.apache.org/activemq/browse/AMQ-630?page=all ]
     
Kieran Murphy reopened AMQ-630:
-------------------------------


This is fixed except when I use failover.  I am using failover (on client side) to connect to a network of brokers configured with static discovery and failover=true.  After the client has connected to some broker in the network, if I bring down all brokers in the network, the client will not shutdown.  Watching the client's DEBUG output, I see that it is forever trying to recoonect to a broker from the failover list.

When I turn off failover on the client side, the reconnection attempts do not continue -- i.e. without failover, the client shuts down properly. With failover, the client is forever trying to reconnect to a broker. I also set maxReconnectAttempts on the client, it still gets this debug output:

DEBUG - Attempting connect to: tcp://localhost:61616
DEBUG - Connect fail to: tcp://localhost:61616, reason: java.net.ConnectException: Connection refused
DEBUG - Waiting 30000 ms before attempting connection.
DEBUG - Waiting for transport to reconnect.
DEBUG - Waiting for transport to reconnect.
DEBUG - Waiting for transport to reconnect.
DEBUG - Waiting for transport to reconnect.
DEBUG - Waiting for transport to reconnect.

...and so on. This prevents the client fromn shutting down.

If I restart a broker, the client reconnects and then completes shutting down.

> After broker has shutdown, cannot shutdown a client application
> ---------------------------------------------------------------
>
>          Key: AMQ-630
>          URL: https://issues.apache.org/activemq/browse/AMQ-630
>      Project: ActiveMQ
>         Type: Bug

>     Versions: 4.0 M4
>     Reporter: Kieran Murphy
>      Fix For: 4.0 RC 2

>
>
> 1.  Bring up a broker
> 2.  Bring up a client application which connects to the broker
> 3.  Stop the broker.
> 4.  Now try to stop the client app -- it will not shutdown until the broker is restarted.  
> Using failover:tcp to connect to broker.

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