[jbossts-issues] [JBoss JIRA] (JBTM-1556) provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling
[
https://issues.jboss.org/browse/JBTM-1556?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on JBTM-1556:
------------------------------------
When each coordinator handles the timeout, does it also cancel its subordinates (as if the
subordinate is one of the resources)? Or is it more like the coordinator times out the
subordinate (as a resource) which means blocking until the subordinate has completed the
subordinate level (reaper) timing out of its (subordinate) resources?
In other words, could the subordinate coordinator Synchronization.afterCompletion() be
called from a transport thread ever or only from a reaper thread?
provide way for Synchronization.afterCompletion callee to know if the
Reaper thread is calling
----------------------------------------------------------------------------------------------
Key: JBTM-1556
URL: https://issues.jboss.org/browse/JBTM-1556
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transaction Core
Affects Versions: 4.17.3
Reporter: Scott Marlow
Assignee: Tom Jenkinson
Fix For: 4.17.4, 5.0.0.M3
When the Synchronization.afterCompletion is invoked for EE JPA containers, knowledge of
whether the current thread is the Reaper thread (cancelling the transaction from a
background thread).
The fix to this jira will help with handling the [JPA 2.1 container concurrency
requirements|http://java.net/projects/jpa-spec/lists/jsr338-experts/archi...].
Please implement the solution makes the most sense to you, as this will introduce an
additional dependency between other systems and JBossTM/JBossTS that depend on the
solution, that will likely be around for a long time.
--
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