-
Component Upgrade
-
Resolution: Done
-
Major
-
None
-
None
Tag: https://code.engineering.redhat.com/gerrit/gitweb?p=messaging/activemq-artemis.git;a=shortlog;h=refs/tags/2.9.0.redhat-00019
Diff: https://code.engineering.redhat.com/gerrit/gitweb?p=messaging/activemq-artemis.git;a=commitdiff;h=2.9.0.redhat-00019;hp=2.9.0.redhat-00017
Shortlog: https://code.engineering.redhat.com/gerrit/gitweb?p=messaging/activemq-artemis.git;a=shortlog;h=2.9.0.redhat-00019;hp=2.9.0.redhat-00017
Commit Hash: d07d812fb66bd3a10963bf4f801311b4b28a03d6
- clones
-
JBEAP-21308 (7.4.z) Upgrade Artemis from 2.16.0.redhat-00022 to 2.16.0.redhat-00032
- Closed
-
WFLY-13226 Upgrade Apache Artemis to 2.16.0
- Closed
- incorporates
-
JBEAP-20996 [QE](7.3.z) ARTEMIS-3120 Artemis keeps logging XA recovery warnings
- Closed
-
JBEAP-18325 [GSS](7.3.z) [WFLY-10725, ENTMQBR-3702] ARTEMIS-2176 Repeating WARN log message "Notified of connection failure" after every xa recovery when read-timeout is configure with a smaller value than default client-failure-check-period (30 seconds)
- Closed
-
JBEAP-20393 [GSS](7.3.z) ARTEMIS-2954 RA doesn't use the RA specified prefix when setting up a destination
- Closed
-
JBEAP-20763 ARTEMIS-3037 JournalImpl#checkKnownRecordID() implementation can leave a thread hanging in WAITING state
- Closed
- relates to
-
JBEAP-20405 [GSS](7.3.z) Upgrade Artemis from 2.9.0.redhat-00016 to 2.9.0.redhat-00017
- Closed