Skip to content

[WFLY-21044]: Not recovered transactions after crash of server with MDB.#19303

Merged
bstansberry merged 3 commits intowildfly:mainfrom
ehsavoie:WFLY-21044
Nov 1, 2025
Merged

[WFLY-21044]: Not recovered transactions after crash of server with MDB.#19303
bstansberry merged 3 commits intowildfly:mainfrom
ehsavoie:WFLY-21044

Conversation

@ehsavoie
Copy link
Member

  • Fixing how WildFly provides the recovery manager to Artemis
  • Removing the old MSC API usage to get the RecoveryService
  • Upgrading Artemis from 2.42.0 to 2.43.0

Jira: https://issues.redhat.com/browse/WFLY-21044
https://issues.redhat.com/browse/WFLY-21063

MDB.

 * Fixing how WildFly provides the recovery manager to Artemis
 * Removing the old MSC API usage to get the RecoveryService

Jira: https://issues.redhat.com/browse/WFLY-21044

Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
* Upgrading Artemis from 2.42 to 2.43.0.
* release Note: https://activemq.apache.org/components/artemis/download/release-notes-2.43.0

Jira: https://issues.redhat.com/browse/WFLY-21063

Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
@mnovak
Copy link
Contributor

mnovak commented Oct 23, 2025

I can confirm this PR is fixing WFLY-21044 and does not cause any regression in messaging.

@github-actions github-actions bot added the deps-ok Dependencies have been checked, and there are no significant changes label Oct 23, 2025
@rhusar rhusar changed the title [WFLY-21044-]: Not recovered transactions after crash of server with MDB. [WFLY-21044]: Not recovered transactions after crash of server with MDB. Oct 23, 2025
@bstansberry
Copy link
Contributor

Is the Artemis update required for the bug fix? If not it's better if they are decoupled.

Copy link
Contributor

@bstansberry bstansberry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After chatting with @ehsavoie I don't object to combining the upgrade with this; I don't think it will delay merging.

But, I suspect the MSC bits need to be ported to 38.x while a minor update or Artemis needs more thought there. So there I suggest separating things.

I've got a minor code review comment though. Sorry; I meant to post that yesterday.

@@ -38,9 +34,6 @@ private static XAResourceRecoveryRegistry getXAResourceRecoveryRegistry() {
// This parsing isn't 100% ideal as it's somewhat 'internal' knowledge of the relationship between
// capability names and service names. But at this point that relationship really needs to become
// a contract anyway
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The comment lines should be removed since they are no longer relevant.

@jmesnil
Copy link
Member

jmesnil commented Oct 31, 2025

But, I suspect the MSC bits need to be ported to 38.x while a minor update or Artemis needs more thought there. So there I suggest separating things.

#19304 is the backport to 38.x (without the artemis upgrade)

Copy link
Contributor

@bstansberry bstansberry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a commit to get rid of the comment.

I don't care about that nit in the 38.x PR; it's just cruft cleanup.

@bstansberry bstansberry merged commit 9917491 into wildfly:main Nov 1, 2025
15 of 16 checks passed
@bstansberry
Copy link
Contributor

Thanks @ehsavoie

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

deps-ok Dependencies have been checked, and there are no significant changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants