Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 900984 - (JBPAPP6-1396) Setting transaction timeout on UserTransaction leaks to the thread and doesn't get cleared
Setting transaction timeout on UserTransaction leaks to the thread and doesn'...
Status: VERIFIED
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB (Show other bugs)
6.0.0
Unspecified Unspecified
urgent Severity urgent
: DR10
: EAP 6.4.0
Assigned To: David M. Lloyd
Jan Martiska
http://jira.jboss.org/jira/browse/JBP...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-03 05:04 EDT by Ravi Bhardwaj
Modified: 2016-07-13 18:47 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker AS7-5641 Major Open Setting transaction timeout on UserTransaction leaks to the thread and doesn't get cleared 2016-12-09 12:28 EST
JBoss Issue Tracker JBPAPP6-1396 Major Closed Setting transaction timeout on UserTransaction leaks to the thread and doesn't get cleared 2016-12-09 12:28 EST

  None (edit)
Description Ravi Bhardwaj 2012-10-03 05:04:10 EDT
Help Desk Ticket Reference: https://gss--c.na7.visual.force.com/apex/Case_View?id=500A000000AvUyo&sfdc.override=1
project_key: JBPAPP6

A user has reported (with an example) that setting a transaction timeout on the UserTransaction will leak the timeout onto the thread and subsequent transaction creation on that thread uses the leaked value instead of new values.

More details in the referenced forum thread and the jira.
Comment 1 Ravi Bhardwaj 2012-10-03 05:05:37 EDT
Link: Added: This issue relates to AS7-5641
Comment 4 tom.jenkinson 2012-10-03 05:43:31 EDT
Hi Ravi,

This got assigned to me but the AS7 issue is assigned to David, so I am assigning it to him.

Thanks,
Tom
Comment 5 Anne-Louise Tangring 2012-11-13 15:57:54 EST
Docs QE Status: Removed: NEW 
Comment 6 David M. Lloyd 2013-03-13 08:29:05 EDT
From the forum thread from jhaliday:
"Per the spec the timeout is NOT scoped to the transaction, it's scoped to the Thread. If you want to reset it, you explicitly call setTransactionTimeout(0). Arguably in a Thread pooled environment it's the job of the pooling logic to do that, to give the user the impression they have a new Thread even when it's actually recycled. But that's for the EJB container to address, not the transaction manager. The TM is not aware of the thread pooling and has no opportunity to do such a reset. This is not a TM bug."

So.. this is not a bug.  How do I reject a BZ?
Comment 7 Ivo Studensky 2013-08-14 06:06:08 EDT
This indeed is a bug. Although it is not a TM bug, it is a bug in the EJB container.
Comment 11 David M. Lloyd 2014-11-13 09:04:39 EST
FWIW my comment #6 is nonsense.  There is a fix just about ready for this issue.
Comment 13 Jan Martiska 2014-11-26 09:05:01 EST
Verified in EAP 6.4.0.DR11

Note You need to log in before you can comment on or make changes to this bug.