You can change the cluster-connection to have a few retries... and tweak other properties.
I'm not sure if you have any infra-structure issue on your network that may push a delay eventually? On Wed, Oct 4, 2017 at 6:29 AM, boris_snp <boris.godu...@spglobal.com> wrote: > Mike, > > I have established network pinger, logging GC's, do not see any network > failures nor prolonged full GC's (4 - 6 seconds). This is what i see in the > logs: > master: > 19:49:56,364 WARN [org.apache.activemq.artemis.core.client] AMQ212037: > Connection failure has been detected: AMQ119014: Did not receive data from > /10.202.147.99:57290 within the 120,000ms connection TTL. The connection > will now be closed. > 19:49:56,366 WARN [org.apache.activemq.artemis.core.server] AMQ222092: > Connection to the backup node failed, removing replication now > slave: > 19:50:49,380 WARN [org.apache.activemq.artemis.core.client] AMQ212037: > Connection failure has been detected: AMQ119011: Did not receive data from > server for > org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnection@6da143b4[local= > /10.202.147.99:57290, remote=nj09mhf0681/10.202.147.99:41410] > [code=CONNECTION_TIMEDOUT] > 19:50:50,456 INFO [org.apache.activemq.artemis.core.server] AMQ221037: > ActiveMQServerImpl::serverUUID=7ffa29a0-7c48-11e7-9784-e83935127b09 to > become 'live' > 19:51:08,837 INFO [org.apache.activemq.artemis.core.server] AMQ221007: > Server is now live > 19:51:13,444 WARN [org.apache.activemq.artemis.core.client] AMQ212034: > There are more than one servers on the network broadcasting the same node > id. > master: > 19:51:13,449 WARN [org.apache.activemq.artemis.core.client] AMQ212034: > There are more than one servers on the network broadcasting the same node > id. > > How can I avoid this? Is there a way to automatically recover from this > state? > Will appreciate any help, > Boris > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html -- Clebert Suconic
