Hi Tim, Sorry for not been clear enough. AMQ1 has IP 10.0.1.53 and its configuration points to 10.0.1.200:61616 AMQ2 has IP 10.0.1.200 and its configuration points to 10.0.1.53:61616
The idea is to keep at least one of these two alive at all times... and if one of them goes down, it would be able to re-join cluster via another one. Make sense? Also... I sort of get over this particular problem by getting rid of AMQW1, AMQW2 and using failover:(tcp://10.0.1.53:61616?wireFormat.maxInactivityDuration=0,tcp://10.0.1.200:61616?wireFormat.maxInactivityDuration=0)?jms.rmIdFromConnectionId=true&initialReconnectDelay=100 as ServerUrl in Wildfly resource-adapter configuration. It mostly work... the only problem now - http://activemq.2283324.n4.nabble.com/ActiveMQ-reports-Successfully-connected-to-and-Failed-to-connect-to-at-the-same-time-tp4702034.html Cheers, Andrei -- View this message in context: http://activemq.2283324.n4.nabble.com/Using-Standalone-ActiveMQ-with-Wildfly-tp4701969p4702225.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
