activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] Created: (AMQ-2904) failover: protocol doesn't work within a static:() URI in a networkConnector
Date Tue, 07 Sep 2010 14:13:40 GMT
failover: protocol doesn't work within a static:() URI in a networkConnector

                 Key: AMQ-2904
             Project: ActiveMQ
          Issue Type: Bug
          Components: Transport
    Affects Versions: 5.4.0
            Reporter: Gary Tully
            Assignee: Gary Tully
             Fix For: 5.4.1

Am configuring a networkConnector, and want it to do failover against two brokers. Xml config
<networkConnectors>            <networkConnector                uri="static:(failover:(tcp://${activemq01.master.networkconnector.ip}:${activemq01.master.openwire.port},tcp://${activemq01.slave.networkconnector.ip}:${activemq01.slave.openwire.port})?randomize=true)"
Problem is, the failoer doesn't work 

When activemq02 connects to activemq01, we see the following on activemq01:
INFO | Connector openwire Started
 INFO | ActiveMQ JMS Message Broker (activemq01, ID:Ade's-52856-1283520722984-0:0) started
 INFO | Connector vm://activemq01 Started
 INFO | Created Duplex Bridge back to activemq02
 INFO | Network connection between vm://activemq01#0 and tcp:///
has been established.{code}
All good! If I take activemq01 down, then on reconnect, we don't see the duplex bridge get
created. This is the output from activemq01.{code}

INFO | Recovery replayed 1 operations from the journal in 0.036 seconds.
 INFO | ActiveMQ 5.4.0-fuse-00-00 JMS Message Broker (activemq01) is starting
 INFO | For help or more information please see:
 INFO | Scheduler using directory: activemq-data/scheduler
 INFO | Listening for connections at: tcp://
 INFO | Connector openwire Started
 INFO | ActiveMQ JMS Message Broker (activemq01, ID:Ade's-52922-1283520881264-0:0) started{code}
Note that there's no mention of a Duplex bridge. The output from the activemq02 broker says:
Transport (/ failed to tcp:// , attempting to automatically
reconnect due to:
 INFO | Outbound transport to activemq01 interrupted.
 INFO | Network connection between vm://activemq02#0 and tcp://
has been established.
 INFO | Outbound transport to activemq01 resumed
 INFO | Successfully reconnected to tcp://
 WARN | Unexpected extra broker info command received: BrokerInfo {commandId = 19, responseRequired
= false, brokerId = ID:Ade's-52922-1283520881264-0:0, brokerURL = tcp://, slaveBroker
= false, masterBroker = false, faultTolerantConfiguration = false, networkConnection = false,
duplexConnection = false, peerBrokerInfos = [], brokerName = activemq01, connectionId = 0,
brokerUploadUrl = null, networkProperties = null}{code}

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message