maybe tune in the broker url the value startuptimeout
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-07-11 13:22 GMT+02:00 [email protected] <[email protected]>: > So the one thing that seems consistent is that activeMQ doesn't seem to > connect and then just all the sudden starts connecting. > > Jul 11, 2016 12:43:42 AM org.apache.activemq.ra.ActiveMQEndpointWorker$1 > run > INFO: Successfully established connection to broker > [failover:(tcp://omaedcotx092.na.corp.ipgnetwork.com:61616 > ,tcp://omaedcotx093.na.corp.ipgnetwork.com:61616)?randomize=false] > Jul 11, 2016 12:43:45 AM > org.apache.activemq.transport.failover.FailoverTransport doReconnect > > I found this article: > > http://activemq.apache.org/javaxjmsjmsexception-wire-format-negociation-timeout-peer-did-not-send-his-wire-format.html > > However, i'm unsure as to how I can implement this properly or where. I > attempted the recommended configuration in tomee.xml but it gave me an > error > for an unknown property. Maybe this wasn't set properly as I assumed it > was > set on the Broker not the failover config. > > This is my current default setting that will eventually start with 2 - 3 > hours of activeMQ Fails and then a sudden hit. > > <Resource id="JmsResourceAdapter" type="ActiveMQResourceAdapter"> > BrokerXmlConfig > broker:(tcp://TomEE1.fqdn:61616)?persistent=true&useJmx=false > ServerUrl = > failover:(tcp://TomEE1.fqdn:61616,tcp://TomEE2.fqdn:61616)?randomize=false > DataSource JmsDS > > > </Resource> > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/ActiveMQ-Connection-Failures-Random-to-Constant-tp4679269p4679280.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
