[jboss-as7-dev] Better handling of transaction leaks?

[Carlo de Wolf]

Yes, I would even say that we need it in the thread pools themselves.
Note that it does not have anything to do with cached connections.

Carlo

On 10/18/2011 05:58 PM, Jaikiran Pai wrote:
> While looking into a test failure I noticed that currently user
> applications can end up leaking transactions (associated with the
> invocation thread):
>
> Servlet {
>
>      doGet() {
>        UserTransaction.begin();
>        doSomeOp();
>        fail();
>        // no tx rollback/commit
>      }
> }
>
> Subsequent transactions on that thread can lead to failures and other
> sorts of issues. Looking back at previous versions of AS, we had a valve
> http://anonsvn.jboss.org/repos/jbossas/trunk/tomcat/src/main/java/org/jboss/web/tomcat/service/jca/CachedConnectionValve.java
> which used to cleanup (and log an error) about the leaking transactions.
>
> Do we want something similar for AS7? Also, are there other "entry
> points" (like servlets for web requests) where such leaks can happen and
> needs to be taken care off?
>
> -Jaikiran
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev