[
https://issues.redhat.com/browse/WFLY-13633?page=com.atlassian.jira.plugi...
]
Thomas Jenkinson commented on WFLY-13633:
-----------------------------------------
This is just a thought, I have not tested or thought the proposal through fully but it
might help in conjunction with [~brian.stansberry]'s synchonization suggestion in
https://issues.redhat.com/browse/WFLY-13633
To not break backwards compatibility in Narayana, perhaps a new operation could be added
to the bean that directly manipulate
https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com...
Something like:
{code}
public void removeCommitMarkableResourceJNDIName(String name) {
synchronized (this) { // not using commitMarkableResourceJNDINames because it could be
changed
commitMarkableResourceJNDINames.remove(name);
}
}
{code}
We might need to protect / synchronize other parts of the code that manipulate
commitMarkableResourceJNDINames and callers that interact with it such as the area that
Brian mentioned but it might get over the initial issue.
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)