-
Component Upgrade
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
Upgrade the integration layer to fix WFLY-17362
Tag: https://github.com/rh-messaging/artemis-wildfly-integration/releases/tag/1.0.7
Diff: https://github.com/rh-messaging/artemis-wildfly-integration/compare/1.0.4...1.0.7
Hash: e5e803ec6716363caebef8af6741763e552152fa
- clones
-
WFLY-17363 Upgrade artemis-wildfly-integration to 1.0.7
-
- Closed
-
- incorporates
-
JBEAP-24371 (7.4.z) Messaging - Transaction remained in prepared state after failover
-
- Closed
-
-
JBEAP-24417 [GSS](7.4.z) 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
-
-
WFLY-18756 WildFly throws UnknownHostExceptions and XARecovery fails when Connected to an AMQ Cluster in OpenShift
-
- Closed
-
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Important: Red Hat JBoss Enterprise Application Platform 7.4.10 security update), and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:1516