Doesn't anyone have any idea?
Didn't I provide enough information? Is the problem too hard to help out with?
It would really help to get some thoughts on disabling the XA recovery. Whether
this is a problem, and whether we're doing it in the right way?
See my last post.
On 16/12/2019, 16:00,
Also, I discovered this warning in the startup of JBoss.
15:47:36,686 WARN [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC
service thread 1-7) IJ020016: Missing element. XA recovery disabled
for: java:/activemq/ConnectionFactory
I even get that when I explicitly add to the
connection-
Maybe some more information;
Here's a recent local logging
14:37:17,865 DEBUG [org.apache.activemq.transport.failover.FailoverTransport]
(Periodic Recovery) Stopped tcp://localhost:61616
14:37:17,866 DEBUG [org.apache.activemq.transport.failover.FailoverTransport]
(Periodic Recovery) Reconnect
Hi all!
We've recently been connecting to another party's broker, with a failover
setup.
We soon discovered we're getting a lot of these:
11:51:36,115 INFO
[org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ Task-1)
Successfully connected to tcp://:61616
Sometimes even a couple
