You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Justin Field (JIRA)" <ji...@apache.org> on 2012/10/30 19:38:12 UTC
[jira] [Updated] (AMQ-4143) Consumers and Producers fail to
failover a second time once a broker comes back online
[ https://issues.apache.org/jira/browse/AMQ-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Field updated AMQ-4143:
------------------------------
Description:
I have 2 brokers embedded using a pure spring configuration on 2 different servers using the exact same config.
When I connect to a broker using jconsole and issue the stop() command to stop the broker (1), the other broker (2) takes over as it should. My application has a quartz job that detects the stopped broker and replaces it with a new broker using a broker factory. When I stop broker 2 the application goes heywire and dumps and socket closed error in an infinite loop.
ERROR TransportConnector.java:228 ActiveMQ Transport Server: tcp://0.0.0.0:61616 ) Could not accept connection : java.net.SocketException: Socket is closed
was:
I have 2 brokers embedded using a pure spring configuration on 2 different servers using the exact same config.
When I connect to a broker using jconsole and issue the stop() command to stop the broker (1), the other broker (2) takes over as it should. My application has a quartz job that detects the stopped broker and replaces it with a new broker using a broker factory. When I stop broker 2 the application goes heywire and dumps and socket closed error in an infinite loop.
> Consumers and Producers fail to failover a second time once a broker comes back online
> --------------------------------------------------------------------------------------
>
> Key: AMQ-4143
> URL: https://issues.apache.org/jira/browse/AMQ-4143
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, Transport
> Affects Versions: 5.7.0
> Environment: Resin 4, Spring 3, Java 1.6, jdbc persistance
> Reporter: Justin Field
>
> I have 2 brokers embedded using a pure spring configuration on 2 different servers using the exact same config.
> When I connect to a broker using jconsole and issue the stop() command to stop the broker (1), the other broker (2) takes over as it should. My application has a quartz job that detects the stopped broker and replaces it with a new broker using a broker factory. When I stop broker 2 the application goes heywire and dumps and socket closed error in an infinite loop.
> ERROR TransportConnector.java:228 ActiveMQ Transport Server: tcp://0.0.0.0:61616 ) Could not accept connection : java.net.SocketException: Socket is closed
--
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