You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Kieran Murphy (JIRA)" <ji...@apache.org> on 2006/11/10 17:52:02 UTC
[jira] Closed: (AMQ-630) After broker has shutdown, cannot shutdown
a client application
[ https://issues.apache.org/activemq/browse/AMQ-630?page=all ]
Kieran Murphy closed AMQ-630.
-----------------------------
Resolution: Fixed
This is fixed, but the client using the failover protocol must be configured with the maxReconnectAttempts argument set. If maxReconnectAttempts is not set, then the client tries forever to reconnect and this seems to block the client's shutdown. As long as maxReconnectAttempts value is non-zero, then the client will be able to shutdown when no brokers are online.
> After broker has shutdown, cannot shutdown a client application
> ---------------------------------------------------------------
>
> Key: AMQ-630
> URL: https://issues.apache.org/activemq/browse/AMQ-630
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.0 M4
> Reporter: Kieran Murphy
> Assigned To: Hiram Chirino
> Fix For: 4.1
>
>
> 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