You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Rohnny Moland <rm...@gmail.com> on 2006/06/30 09:41:23 UTC
Automatically reconnect if broker is down
Hi,
Is there a way I can automatically reconnect/subscribe to the broker if
its down? E.g when doing bi-directional messaging where node A and B are
both server and client. I could of course create my own connection class
and try to reconnect every 10 secs or something.
Best regards,
Rohnny
Re: Automatically reconnect if broker is down
Posted by Hiram Chirino <hi...@hiramchirino.com>.
yes that should work too.
On 6/30/06, massive.boisson <ma...@gmail.com> wrote:
>
>
> Can I use
> failover:SSL://host:port
> instead of
> failover:TCP://host:port
> ?
>
> --MB
> --
> View this message in context:
> http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5128517
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
Re: Automatically reconnect if broker is down
Posted by "massive.boisson" <ma...@gmail.com>.
Can I use
failover:SSL://host:port
instead of
failover:TCP://host:port
?
--MB
--
View this message in context: http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5128517
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Automatically reconnect if broker is down
Posted by maquanjun <ma...@gmail.com>.
this is the console of server108
[root@server108 bin]# ./activemq
ACTIVEMQ_HOME: /usr/local/activemq-4.0.1
Loading message broker from: xbean:activemq.xml
INFO BrokerService - ActiveMQ 4.0.1 JMS Message Broker
(TESTBROKER) is starting
INFO BrokerService - For help or more information please
see: http://incubator.apache.org/activemq/
INFO JDBCPersistenceAdapter - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
INFO JournalPersistenceAdapter - Journal Recovery Started from: Active
Journal: using 5 x 20.0 Megs at: /usr/local/acti
vemq-4.0.1/activemq-data/journal
INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in
transactions recovered.
INFO TransportServerThreadSupport - Listening for connections at:
tcp://server108:61616
INFO TransportConnector - Connector default Started
INFO TransportServerThreadSupport - Listening for connections at:
tcp://server108:61613?wireFormat=stomp
INFO TransportConnector - Connector stomp Started
INFO NetworkConnector - Establishing network connection
between from vm://TESTBROKER?network=true to failover:
tcp://server107:61616
INFO VMTransportFactory - binding to broker: TESTBROKER
INFO TransportConnector - Connector vm://TESTBROKER Started
INFO DemandForwardingBridge - Starting a network connection between
vm://TESTBROKER#0 and unconnected has been estab
lished.
INFO DemandForwardingBridge - Network connection between
vm://TESTBROKER#0 and tcp://server107:61616(TESTBROKER) has
been established.
INFO NetworkConnector - Establishing network connection
between from vm://TESTBROKER?network=true to failover:
tcp://server109:61616
INFO DemandForwardingBridge - Starting a network connection between
vm://TESTBROKER#2 and unconnected has been estab
lished.
INFO NetworkConnector - Network Connector default Started
INFO BrokerService - ActiveMQ JMS Message Broker
(TESTBROKER, ID:server108-53862-1151998530225-1:0) started
WARN DemandForwardingBridge - Outbound transport to TESTBROKER
interrupted ...
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008764 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008764 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008735 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008735 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008760 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008760 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008759 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008759 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008753 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008753 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008748 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008748 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008749 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008749 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008754 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008754 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008736 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008736 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008734 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008734 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008751 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008751 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008752 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008752 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008755 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008755 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008738 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1008738 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
INFO DemandForwardingBridge - Outbound transport to TESTBROKER
resumed
INFO DemandForwardingBridge - Network connection between
vm://TESTBROKER#0 and tcp://server107:61616(TESTBROKER) has
been established.
INFO Service - Sync error occurred:
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1011642 already connected
javax.jms.InvalidClientIDException: Broker: TESTBROKER - Client:
ID:localhost.localdomain-58642-1151923038318-1:1011642 alrea
dy connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
at
org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:82)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
at
org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
WARN DemandForwardingBridge - Outbound transport to TESTBROKER
interrupted ...
WARN ManagedTransportConnection - Failed to unregister mbean:
org.apache.activemq:BrokerName=TESTBROKER,Type=Connection,
ConnectorName=default,Connection=2259
INFO BrokerService - ActiveMQ Message Broker (TESTBROKER,
ID:server108-53862-1151998530225-1:0) is shutting
down
INFO VMTransportFactory - Shutting down VM connectors for
broker: TESTBROKER
INFO VMTransportFactory - Shutting down VM connectors for
broker: TESTBROKER
INFO TransportConnector - Connector vm://TESTBROKER Stopped
INFO NetworkConnector - Network Connector default Stopped
INFO TransportConnector - Connector default Stopped
INFO TransportConnector - Connector stomp Stopped
INFO VMTransportFactory - Shutting down VM connectors for
broker: TESTBROKER
INFO BrokerService - ActiveMQ JMS Message Broker
(TESTBROKER, ID:server108-53862-1151998530225-1:0) stopped
[root@server108 bin]#
--
View this message in context: http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5163209
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Automatically reconnect if broker is down
Posted by maquanjun <ma...@gmail.com>.
this is the console of server107
[root@server107 bin]# ./activemq
ACTIVEMQ_HOME: /usr/local/activemq-4.0.1
Loading message broker from: xbean:activemq.xml
INFO BrokerService - ActiveMQ 4.0.1 JMS Message Broker
(TESTBROKER) is starting
INFO BrokerService - For help or more information please
see: http://incubator.apache.org/activemq/
INFO JDBCPersistenceAdapter - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
INFO JournalPersistenceAdapter - Journal Recovery Started from: Active
Journal: using 5 x 20.0 Megs at: /usr/local/acti
vemq-4.0.1/activemq-data/journal
INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in
transactions recovered.
INFO TransportServerThreadSupport - Listening for connections at:
tcp://server107:61616
INFO TransportConnector - Connector default Started
INFO TransportServerThreadSupport - Listening for connections at:
tcp://server107:61613?wireFormat=stomp
INFO TransportConnector - Connector stomp Started
INFO NetworkConnector - Establishing network connection
between from vm://TESTBROKER?network=true to failover:
tcp://server108:61616
INFO VMTransportFactory - binding to broker: TESTBROKER
INFO TransportConnector - Connector vm://TESTBROKER Started
INFO DemandForwardingBridge - Starting a network connection between
vm://TESTBROKER#0 and unconnected has been estab
lished.
INFO NetworkConnector - Establishing network connection
between from vm://TESTBROKER?network=true to failover:
tcp://server109:61616
INFO DemandForwardingBridge - Network connection between
vm://TESTBROKER#0 and tcp://server108:61616(TESTBROKER) has
been established.
INFO DemandForwardingBridge - Starting a network connection between
vm://TESTBROKER#2 and unconnected has been estab
lished.
INFO NetworkConnector - Network Connector default Started
INFO BrokerService - ActiveMQ JMS Message Broker
(TESTBROKER, ID:server107-38703-1151998634173-1:0) started
INFO BrokerService - ActiveMQ Message Broker (TESTBROKER,
ID:server107-38703-1151998634173-1:0) is shutting
down
INFO VMTransportFactory - Shutting down VM connectors for
broker: TESTBROKER
INFO VMTransportFactory - Shutting down VM connectors for
broker: TESTBROKER
INFO TransportConnector - Connector vm://TESTBROKER Stopped
INFO NetworkConnector - Network Connector default Stopped
INFO TransportConnector - Connector default Stopped
INFO TransportConnector - Connector stomp Stopped
INFO VMTransportFactory - Shutting down VM connectors for
broker: TESTBROKER
INFO BrokerService - ActiveMQ JMS Message Broker
(TESTBROKER, ID:server107-38703-1151998634173-1:0) stopped
[root@server107 bin]#
[root@server107 bin]#
--
View this message in context: http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5163203
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Automatically reconnect if broker is down
Posted by maquanjun <ma...@gmail.com>.
this is the console of server 107
[root@server107 bin]# ./activemq
ACTIVEMQ_HOME: /usr/local/activemq-4.0.1
Loading message broker from: xbean:activemq.xml
INFO BrokerService - ActiveMQ 4.0.1 JMS Message Broker
(TESTBROKER) is starting
INFO BrokerService - For help or more information please
see: http://incubator.apache.org/activemq/
INFO JDBCPersistenceAdapter - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
INFO JournalPersistenceAdapter - Journal Recovery Started from: Active
Journal: using 5 x 20.0 Megs at: /usr/local/acti
vemq-4.0.1/activemq-data/journal
INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in
transactions recovered.
INFO TransportServerThreadSupport - Listening for connections at:
tcp://server107:61616
INFO TransportConnector - Connector default Started
INFO TransportServerThreadSupport - Listening for connections at:
tcp://server107:61613?wireFormat=stomp
INFO TransportConnector - Connector stomp Started
INFO NetworkConnector - Establishing network connection
between from vm://TESTBROKER?network=true to failover:
tcp://server108:61616
INFO VMTransportFactory - binding to broker: TESTBROKER
INFO TransportConnector - Connector vm://TESTBROKER Started
INFO DemandForwardingBridge - Starting a network connection between
vm://TESTBROKER#0 and unconnected has been estab
lished.
INFO NetworkConnector - Establishing network connection
between from vm://TESTBROKER?network=true to failover:
tcp://server109:61616
INFO DemandForwardingBridge - Network connection between
vm://TESTBROKER#0 and tcp://server108:61616(TESTBROKER) has
been established.
INFO DemandForwardingBridge - Starting a network connection between
vm://TESTBROKER#2 and unconnected has been estab
lished.
INFO NetworkConnector - Network Connector default Started
INFO BrokerService - ActiveMQ JMS Message Broker
(TESTBROKER, ID:server107-38703-1151998634173-1:0) started
INFO BrokerService - ActiveMQ Message Broker (TESTBROKER,
ID:server107-38703-1151998634173-1:0) is shutting
down
INFO VMTransportFactory - Shutting down VM connectors for
broker: TESTBROKER
INFO VMTransportFactory - Shutting down VM connectors for
broker: TESTBROKER
INFO TransportConnector - Connector vm://TESTBROKER Stopped
INFO NetworkConnector - Network Connector default Stopped
INFO TransportConnector - Connector default Stopped
INFO TransportConnector - Connector stomp Stopped
INFO VMTransportFactory - Shutting down VM connectors for
broker: TESTBROKER
INFO BrokerService - ActiveMQ JMS Message Broker
(TESTBROKER, ID:server107-38703-1151998634173-1:0) stopped
[root@server107 bin]#
--
View this message in context: http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5163184
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Automatically reconnect if broker is down
Posted by maquanjun <ma...@gmail.com>.
I increase initialReconnectDelay to 20000 ,everything is the same.
I comment the networkConnector, everything is the same.
--
View this message in context: http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5163813
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Automatically reconnect if broker is down
Posted by James Strachan <ja...@gmail.com>.
I've no idea why this doesn't work for you - its working for others in
all the testing.
On 7/6/06, maquanjun <ma...@gmail.com> wrote:
>
> Hi James,
> Is there any idea? ;)
>
> --
> View this message in context: http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5193081
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: Automatically reconnect if broker is down
Posted by maquanjun <ma...@gmail.com>.
Hi James,
Is there any idea? ;)
--
View this message in context: http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5193081
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Automatically reconnect if broker is down
Posted by James Strachan <ja...@gmail.com>.
So it looks like your problem could be that you have a demand
forwarding network among brokers and when the client tries to
reconnect it thinks its already got a connection from that client
(from the original broker) and so its rejecting the connection via a
duplicate Client ID exception.
I wonder if you increase the initialReconnectDelay to something like
1000 or 2000 does that help? It sounds like a timing bug though. I
wonder if removing the network connector (commenting out the
<networkConnector> in the activemq.xml files) would be a temporary
workaround.
On 7/4/06, maquanjun <ma...@gmail.com> wrote:
>
> The following is the command I excuted ,and when I stop the server107 ,this
> consumertool stopped at once
>
> C:\jdk1.5\bin\java -classpath
> "C:\work\test\activemqtest\classes;C:\work\test\activemqtest\lib\activeio-core-3.0-beta3.jar;C:\work\test\activemqtest\lib\activemq-console-4.0.1.jar;C:\work\test\activemqtest\lib\activemq-core-4.0.1.jar;C:\work\test\activemqtest\lib\activemq-optional-4.0.1.jar;C:\work\test\activemqtest\lib\incubator-activemq-4.0.1.jar;C:\work\test\activemqtest\lib\backport-util-concurrent-2.1.jar;C:\work\test\activemqtest\lib\commons-logging-1.0.4.jar;C:\work\test\activemqtest\lib\geronimo-j2ee-management_1.0_spec-1.0.jar;C:\work\test\activemqtest\lib\geronimo-jms_1.1_spec-1.0.jar;C:\work\test\activemqtest\lib\mx4j-2.1.1.jar;C:\javalib\apache\log4j\log4j-1.2.13.jar;C:\jdk1.5\lib\jconsole.jar;C:\jdk1.5\lib\tools.jar;C:\jdk1.5\lib\htmlconverter.jar;C:\jdk1.5\lib\dt.jar;C:\jdk1.5\jre\lib\jsse.jar;C:\jdk1.5\jre\lib\im\indicim.jar;C:\jdk1.5\jre\lib\im\thaiim.jar;C:\jdk1.5\jre\lib\jce.jar;C:\jdk1.5\jre\lib\deploy.jar;C:\jdk1.5\jre\lib\javaws.jar;C:\jdk1.5\jre\lib\charsets.jar;C:\jdk1.5\jre\lib\rt.jar;C:\jdk1.5\jre\lib\ext\dnsns.jar;C:\jdk1.5\jre\lib\ext\sunpkcs11.jar;C:\jdk1.5\jre\lib\ext\localedata.jar;C:\jdk1.5\jre\lib\ext\sunjce_provider.jar;C:\jdk1.5\jre\lib\plugin.jar"
> org.apache.activemq.tool.ConsumerTool
> failover:(tcp://server107:61616,tcp://server108:61616,tcp://server109:61616)?initialReconnectDelay=100
> false
> Connecting to URL:
> failover:(tcp://server107:61616,tcp://server108:61616,tcp://server109:61616)?initialReconnectDelay=100
> Consuming queue: TOOL.DEFAULT
> Using non-durable subscription
>
> --
> View this message in context: http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5163248
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: Automatically reconnect if broker is down
Posted by maquanjun <ma...@gmail.com>.
The following is the command I excuted ,and when I stop the server107 ,this
consumertool stopped at once
C:\jdk1.5\bin\java -classpath
"C:\work\test\activemqtest\classes;C:\work\test\activemqtest\lib\activeio-core-3.0-beta3.jar;C:\work\test\activemqtest\lib\activemq-console-4.0.1.jar;C:\work\test\activemqtest\lib\activemq-core-4.0.1.jar;C:\work\test\activemqtest\lib\activemq-optional-4.0.1.jar;C:\work\test\activemqtest\lib\incubator-activemq-4.0.1.jar;C:\work\test\activemqtest\lib\backport-util-concurrent-2.1.jar;C:\work\test\activemqtest\lib\commons-logging-1.0.4.jar;C:\work\test\activemqtest\lib\geronimo-j2ee-management_1.0_spec-1.0.jar;C:\work\test\activemqtest\lib\geronimo-jms_1.1_spec-1.0.jar;C:\work\test\activemqtest\lib\mx4j-2.1.1.jar;C:\javalib\apache\log4j\log4j-1.2.13.jar;C:\jdk1.5\lib\jconsole.jar;C:\jdk1.5\lib\tools.jar;C:\jdk1.5\lib\htmlconverter.jar;C:\jdk1.5\lib\dt.jar;C:\jdk1.5\jre\lib\jsse.jar;C:\jdk1.5\jre\lib\im\indicim.jar;C:\jdk1.5\jre\lib\im\thaiim.jar;C:\jdk1.5\jre\lib\jce.jar;C:\jdk1.5\jre\lib\deploy.jar;C:\jdk1.5\jre\lib\javaws.jar;C:\jdk1.5\jre\lib\charsets.jar;C:\jdk1.5\jre\lib\rt.jar;C:\jdk1.5\jre\lib\ext\dnsns.jar;C:\jdk1.5\jre\lib\ext\sunpkcs11.jar;C:\jdk1.5\jre\lib\ext\localedata.jar;C:\jdk1.5\jre\lib\ext\sunjce_provider.jar;C:\jdk1.5\jre\lib\plugin.jar"
org.apache.activemq.tool.ConsumerTool
failover:(tcp://server107:61616,tcp://server108:61616,tcp://server109:61616)?initialReconnectDelay=100
false
Connecting to URL:
failover:(tcp://server107:61616,tcp://server108:61616,tcp://server109:61616)?initialReconnectDelay=100
Consuming queue: TOOL.DEFAULT
Using non-durable subscription
--
View this message in context: http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5163248
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Automatically reconnect if broker is down
Posted by James Strachan <ja...@gmail.com>.
Could you show the console output and the command you typed please?
On 7/4/06, maquanjun <ma...@gmail.com> wrote:
>
> almost as soon as I stop the server
> --
> View this message in context: http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5162976
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: Automatically reconnect if broker is down
Posted by maquanjun <ma...@gmail.com>.
almost as soon as I stop the server
--
View this message in context: http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5162976
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Automatically reconnect if broker is down
Posted by James Strachan <ja...@gmail.com>.
On 7/4/06, maquanjun <ma...@gmail.com> wrote:
>
> Thank you!
>
> I am using 4.0.1 ,the newest version.
> I test the ConsumerTool by
> failover:(tcp://server107:61616,tcp://server108:61616,tcp://server109:61616)?initialReconnectDelay=100&useExponentialBackOff=true
>
> when I stop the connected server, the ConsumerTool will exit too.
How long do you leave it for before the consumer tool exits?
Any chance you could enable debugging and post the log?
http://incubator.apache.org/activemq/how-can-i-enable-detailed-logging.html
--
James
-------
http://radio.weblogs.com/0112098/
Re: Automatically reconnect if broker is down
Posted by maquanjun <ma...@gmail.com>.
Thank you!
I am using 4.0.1 ,the newest version.
I test the ConsumerTool by
failover:(tcp://server107:61616,tcp://server108:61616,tcp://server109:61616)?initialReconnectDelay=100&useExponentialBackOff=true
when I stop the connected server, the ConsumerTool will exit too.
--
View this message in context: http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5162809
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Automatically reconnect if broker is down
Posted by James Strachan <ja...@gmail.com>.
Are you using 4.x? As this was a limitation of 3.x
On 7/4/06, maquanjun <ma...@gmail.com> wrote:
>
> Hi,I use the failover url.
> But I found it only work for producer.
> When a connection used by a cosumer brokes, the consumer will not reconnect
> .
> Any idea?
>
> thank you!
> --
> View this message in context: http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5161621
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: Automatically reconnect if broker is down
Posted by maquanjun <ma...@gmail.com>.
Hi,I use the failover url.
But I found it only work for producer.
When a connection used by a cosumer brokes, the consumer will not reconnect
.
Any idea?
thank you!
--
View this message in context: http://www.nabble.com/Automatically-reconnect-if-broker-is-down-tf1871778.html#a5161621
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Automatically reconnect if broker is down
Posted by James Strachan <ja...@gmail.com>.
On 6/30/06, Rohnny Moland <rm...@gmail.com> wrote:
> Hi,
>
> Is there a way I can automatically reconnect/subscribe to the broker if
> its down? E.g when doing bi-directional messaging where node A and B are
> both server and client. I could of course create my own connection class
> and try to reconnect every 10 secs or something.
The FAQ has this one covered
http://incubator.apache.org/activemq/faq.html
here
http://incubator.apache.org/activemq/how-can-i-support-auto-reconnection.html
--
James
-------
http://radio.weblogs.com/0112098/