[JBoss JIRA] (AS7-5641) Setting transaction timeout on UserTransaction leaks to the thread and doesn't get cleared
5:06 a.m.
jaikiran pai created AS7-5641:
---------------------------------
Summary: Setting transaction timeout on UserTransaction leaks to the thread
and doesn't get cleared
Key: AS7-5641
URL: https://issues.jboss.org/browse/AS7-5641
Project: Application Server 7
Issue Type: Bug
Components: EE, Transactions
Affects Versions: 7.1.3.Final (EAP)
Reporter: jaikiran pai
Assignee: David Lloyd
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.
--
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
5:06 a.m.
[
https://issues.jboss.org/browse/AS7-5641?page=com.atlassian.jira.plugin.s...
]
SBS JIRA Integration updated AS7-5641:
--------------------------------------
Forum Reference: https://community.jboss.org/message/761475#761475 (was:
https://community.jboss.org/message/761475#761475)
Setting transaction timeout on UserTransaction leaks to the thread
and doesn't get cleared
------------------------------------------------------------------------------------------
Key: AS7-5641
URL: https://issues.jboss.org/browse/AS7-5641
Project: Application Server 7
Issue Type: Bug
Components: EE, Transactions
Affects Versions: 7.1.3.Final (EAP)
Reporter: jaikiran pai
Assignee: David Lloyd
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.
--
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
7:18 a.m.
[
https://issues.jboss.org/browse/AS7-5641?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-5641:
-------------------------------------
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 it sounds like we need to make sure we clear this as part of the EE setup actions.
Setting transaction timeout on UserTransaction leaks to the thread
and doesn't get cleared
------------------------------------------------------------------------------------------
Key: AS7-5641
URL: https://issues.jboss.org/browse/AS7-5641
Project: Application Server 7
Issue Type: Bug
Components: EE, Transactions
Affects Versions: 7.1.3.Final (EAP)
Reporter: jaikiran pai
Assignee: David Lloyd
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.
--
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
8:31 a.m.
[
https://issues.jboss.org/browse/AS7-5641?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-5641:
-----------------------------------
{quote}
So it sounds like we need to make sure we clear this as part of the EE setup actions.
{quote}
IMO, this should be done one level higher i.e. even outside of EE since non-EE
applications deployed on the server who get access to UserTransaction (however which way
they do so) could set the tx timeout and that might affect other EE/non-EE applications
since that timeout will leak on the thread.
Setting transaction timeout on UserTransaction leaks to the thread
and doesn't get cleared
------------------------------------------------------------------------------------------
Key: AS7-5641
URL: https://issues.jboss.org/browse/AS7-5641
Project: Application Server 7
Issue Type: Bug
Components: EE, Transactions
Affects Versions: 7.1.3.Final (EAP)
Reporter: jaikiran pai
Assignee: David Lloyd
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.
--
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
4487
days inactive
4487
days old
3 comments
3 participants
participants (3)
-
jaikiran pai (JIRA) -
SBS JIRA Integration (JIRA)
-
Stuart Douglas (JIRA)