-
Bug
-
Resolution: Done
-
Major
-
7.4.8.GA
-
None
In EAP 7.4 it is possible to define connections outside the default broker. When periodic recovery is trying to recovery such XA resource it seems to fail because the port it's trying to use does not exist.
WARN [org.apache.activemq.artemis.service.extensions.xa.recovery] (Periodic Recovery) AMQ172015: Can not connect to XARecoveryConfig [transportConfiguration=[TransportConfiguration(name=, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=amq-broker-cluster-local], discoveryConfiguration=null, username=quickuser, password=****] on auto-generated resource recovery: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007: Cannot connect to server(s). Tried with all available servers.]
In the above example the host is amq-broker-cluster-local but port is 443 since it's a SSL connection.
I'm not sure why recovery process picks up port 61616 it is nowhere in my configuration.
The configuration is setting up a JMS bridge between EAP and external AMQ 7.8.2 broker running in OCP.
If the useTopology is set to false, reuse the initial connection connectors to connect to the broker for recovery
- is incorporated by
-
JBEAP-24383 [GSS](7.4.z) Upgrade artemis-wildfly-integration from 1.0.4 to 1.0.7
-
- Closed
-
- relates to
-
-
- Verified
-
-
-
- Resolved
-
