[jboss-jira] [JBoss JIRA] (WFLY-5536) Recovery manager is not able to recover MDB and shows warnings on each run.
Martyn Taylor (JIRA)
issues at jboss.org
Wed Oct 28 05:35:00 EDT 2015
[ https://issues.jboss.org/browse/WFLY-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122762#comment-13122762 ]
Martyn Taylor commented on WFLY-5536:
-------------------------------------
IIUC the only thing the TM needs from the XAResourceWrapper.getJNDI is a unique string that identifies the resource manager. In Artemis it is possible to have a single connection factory (with a single JNDI) talk to multiple servers (resource managers) for example in a clustered environment. This is the reason we append the NodeID to the JNDI name. It is a bit of a hack imo but this is the solution we agreed on with TX and Artemis guys.
The JNDI name is still present in this scenario from what I can see from [~jmesnil] post which should be enough information for the TM. So I can not see any reason why it should fail to remove the log entry. That said I will replicate this locally and see if there is another underlying issue with Artemis XAResources.
> Recovery manager is not able to recover MDB and shows warnings on each run.
> ---------------------------------------------------------------------------
>
> Key: WFLY-5536
> URL: https://issues.jboss.org/browse/WFLY-5536
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.CR2
> Reporter: Hayk Hovsepyan
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: MDB_JMS_XA.log
>
>
> Recovery manager is not able to recover MDB and shows warnings.
> This causes to see the same warning log in server each time recovery is run.
> This happens when server is crashed before transaction state is saved.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list