[jboss-jira] [JBoss JIRA] Commented: (JBAS-3242) EE spec requires that web container aborts any active txn at the end of a request
Gavin King (JIRA)
jira-events at jboss.com
Fri Aug 4 10:05:12 EDT 2006
[ http://jira.jboss.com/jira/browse/JBAS-3242?page=comments#action_12340629 ]
Gavin King commented on JBAS-3242:
----------------------------------
Of *course* this should be enabled by default.
(1) it is REQUIRED BY THE JAVA EE SPEC!
(2) it is required for stability/robustness. Very few real-life applications properly test that they rollback all transactions in all exceptional cases. If this is not the default, then a single failure in one transaction can result in failures of other subsequent transactions, along with locks retained on resources affecting performance, etc, etc.
Again, this is TOTALLY EVIL behavior.
> 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
More information about the jboss-jira
mailing list