[
https://issues.redhat.com/browse/WFLY-13633?page=com.atlassian.jira.plugi...
]
Michael Musgrove commented on WFLY-13633:
-----------------------------------------
CMR resources can be added using wildfly CLI operations. I believe those operations
require a reload if they are modified. Will that not protect us from the scenario outlined
in the JIRA description
Undeployed CMR resource JNDI names are not deregisted as needing to
be treated as CMR
-------------------------------------------------------------------------------------
Key: WFLY-13633
URL:
https://issues.redhat.com/browse/WFLY-13633
Project: WildFly
Issue Type: Bug
Components: Transactions
Reporter: Thomas Jenkinson
Assignee: Michael Musgrove
Priority: Blocker
https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java...
does not remove the JNDI name from the list of names that Narayana will treat as CMR
resources as it is removed from a copy of the map:
https://github.com/jbosstm/narayana/blob/48818111d12d2e51b52082a00bcb6060...
This means that if Narayana encounters another resource at a later time with the same
JNDI name it will consider it is a CMR resource.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)