[jira] Commented: (AMQ-630) After broker has shutdown, cannot shutdown a client application

["Kieran Murphy (JIRA)" <ji...@activemq.org>]

    [ http://jira.activemq.org/jira//browse/AMQ-630?page=comments#action_35931 ] 

Kieran Murphy commented on AMQ-630:
-----------------------------------

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 the 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 the broker, the client reconnect and then completes shutting down.

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

>     Versions: 4.0 M4
>     Reporter: Kieran Murphy
>      Fix For: 4.0 RC1

>
>
> 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:
   http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira