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 <[EMAIL PROTECTED]> 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/
