-
Bug
-
Resolution: Done
-
Major
-
30.0.0.Final
When the JBoss EAP is running outside OpenShift with its messaging-activemq subsystem iconfigured as a resource adapter connecting to an AMQ cluster within OpenShift, we see UnknownHostExceptions and XARecovery failures due to topology updates, even if useTopologyForLoadBalancing is set to false and even if ha is also set false.
- clones
-
JBEAP-24417 [GSS](7.4.z) JBoss throws UnknownHostExceptions and XARecovery fails when Connected to an AMQ Cluster in OpenShift
- Closed
- is cloned by
-
JBEAP-25239 [GSS](8.0.z) JBoss throws UnknownHostExceptions and XARecovery fails when Connected to an AMQ Cluster in OpenShift
- Closed
- is incorporated by
-
JBEAP-24383 [GSS](7.4.z) Upgrade artemis-wildfly-integration from 1.0.4 to 1.0.7
- Closed
- is related to
-
ENTMQBR-7541 JBoss throws UnknownHostExceptions and XARecovery fails when Connected to an AMQ Cluster in OpenShift
- Closed
-
JBEAP-24522 [GSS](7.4.z) AMQ172015: Can not connect to XARecoveryConfig
- Closed
-
JBEAP-25600 [GSS](7.4.z) WFLY-18212 - If the messaging HA cluster is not full started then the transaction recovery will be misconfigured
- Closed
- links to