Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 900984 (JBPAPP6-1396)

Summary:	Setting transaction timeout on UserTransaction leaks to the thread and doesn't get cleared
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Ravi Bhardwaj <rbhardwa>
Component:	EJB	Assignee:	David M. Lloyd <david.lloyd>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jan Martiska <jmartisk>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.0.0	CC:	dimitris, dosoudil, istudens, kkhan, ochaloup, sjadhav
Target Milestone:	DR10
Target Release:	EAP 6.4.0
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBPAPP6-1396
Whiteboard:
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:	---	Target Upstream Version:
Embargoed:

Description Ravi Bhardwaj 2012-10-03 09:04:10 UTC

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 09:05:37 UTC

Link: Added: This issue relates to AS7-5641

Comment 2 Ravi Bhardwaj 2012-10-03 09:07:25 UTC

SourceForge Reference: Added: https://gss--c.na7.visual.force.com/apex/Case_View?id=500A000000AvUyo&sfdc.override=1
Forum Reference: Removed: https://community.jboss.org/thread/205790 Added: https://community.jboss.org/thread/205790

Comment 3 Ravi Bhardwaj 2012-10-03 09:10:33 UTC

Help Desk Ticket Reference: Added: https://gss--c.na7.visual.force.com/apex/Case_View?id=500A000000AvUyo&sfdc.override=1
SourceForge Reference: Removed: https://gss--c.na7.visual.force.com/apex/Case_View?id=500A000000AvUyo&sfdc.override=1 
Forum Reference: Removed: https://community.jboss.org/thread/205790 Added: https://community.jboss.org/thread/205790

Comment 4 tom.jenkinson 2012-10-03 09:43:31 UTC

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 20:57:54 UTC

Docs QE Status: Removed: NEW

Comment 6 David M. Lloyd 2013-03-13 12:29:05 UTC

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 10:06:08 UTC

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 14:04:39 UTC

FWIW my comment #6 is nonsense.  There is a fix just about ready for this issue.

Comment 13 Jan Martiska 2014-11-26 14:05:01 UTC

Verified in EAP 6.4.0.DR11