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

[Remy Maucherat]

On Wed, 2011-10-19 at 19:29 +0200, Carlo de Wolf wrote:
> On 10/19/2011 04:27 PM, Remy Maucherat wrote:
> > On Wed, 2011-10-19 at 19:25 +0530, Jaikiran Pai wrote:
> >> I agree that there should be a way to easily disable this. The only real
> >> reason why I am in favour of this simple check/cleanup is to ensure that
> >> some rogue application (which doesn't handle transactions correctly)
> >> doesn't end up breaking/affecting some other (well-written) application
> >> deployed on the same instance.
> > A rogue application will be able to trivially do something that would
> > affect other applications in the same instance, I believe.
> >
> EE.4.2.2 Transaction in Web Component Life Cycles
> Returning from the service method to the network client with an active 
> transaction
> context is an error. The web container is required to detect this error 
> and abort the
> transaction.
> 
> How do you propose we implement this?

I didn't know it was a spec requirement :) Old legacy item, probably. So
you win, congratulations, let's make our product worse.

-- 
Remy Maucherat <rmaucher at redhat.com>
Red Hat Inc