[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:
------------------------------------
As part of the fix for AS7-6586, I hard coded the reaper thread name. Please don't
change the reaper thread name until JBTM-1556 offers a way for AS to get the reaper thread
name in a cleaner fashion. If the reaper thread name is changed and JBTM-1556 isn't
fixed, one of the unit tests for AS7-6586 will fail.
If for some reason, you decide not to fix JBTM-1556, please let me know so I can check for
the reaper thread canceling the tx some other way (not sure how).
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
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