[jboss-jira] [JBoss JIRA] Commented: (JBAS-3242) EE spec requires that web container aborts any active txn at the end of a request
[ http://jira.jboss.com/jira/browse/JBAS-3242?page=comments#action_12340619 ]
Remy Maucherat commented on JBAS-3242:
--------------------------------------
At the end of server.xml in the Tomcat SAR, there is:
<!-- Uncomment to check for unclosed connections and transaction terminated
checks
in servlets/jsps.
Important: You need to uncomment the dependency on the
CachedConnectionManager
in META-INF/jboss-service.xml
<Valve
className="org.jboss.web.tomcat.tc6.jca.CachedConnectionValve"
cachedConnectionManagerObjectName="jboss.jca:service=CachedConnectionManager"
transactionManagerObjectName="jboss:service=TransactionManager"
/>
-->
EE spec requires that web container aborts any active txn at the end
of a request
---------------------------------------------------------------------------------
Key: JBAS-3242
URL: http://jira.jboss.com/jira/browse/JBAS-3242
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-4.0.4.GA
Reporter: Gavin King
Assigned To: Remy Maucherat
Priority: Critical
Fix For: JBossAS-4.0.6.CR1
The Java EE spec requires that if there is any active JTA transaction at the end of a
servlet request, then the container must abort the txn. JBoss currently does not do this.
Instead it leaves orphaned transactions dangling about on pooled threads, ready and
waiting to be resumed by any random request that comes along.
This is really Bad behavior and I'm kinda shocked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira