[
https://issues.jboss.org/browse/JBTM-1718?page=com.atlassian.jira.plugin....
]
Mark Little commented on JBTM-1718:
-----------------------------------
Is this really an issue at the moment? Until/unless someone really complains about this, I
think we should wait before breaking compliance with the standard. Interoperability and
portability are very important and whilst it can be argued that all other implementations
would suffer the same problem, I think we don't have enough user input to really know
how important this is when compared to other issues.
Resolve the ParticipantCompletion race condition
------------------------------------------------
Key: JBTM-1718
URL:
https://issues.jboss.org/browse/JBTM-1718
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: TXFramework
Reporter: Paul Robinson
Assignee: Gytis Trikleris
Fix For: 5.0.0.M4
This issue is documented here: JBTM-1429
In the documentation for JBTM-1429, we state that this issue is unlikely to happen in a
distributed environment. This is true, however, the Compensations API is designed to work
local-only as well as distributed over WS-BA. Therefore it is much more likely to happen
in a production environment.
Therefore we need to remove this race condition. It can be done in a proprietary mannor
as we are not interoperating with another implementation ion local-only mode. When
distributing the transaction we fall back to the standard protocol that is susceptible to
the race condition. However, as we stated in the docs, this condition is unlikely to
manifest in a distributed environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira