<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 12pt; color: #000000'><br><br><hr id="zwchr"><blockquote id="DWT8145" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Carlo de Wolf" <cdewolf@redhat.com><br><b>To: </b>jboss-as7-dev@lists.jboss.org<br><b>Sent: </b>Wednesday, October 19, 2011 12:04:33 PM<br><b>Subject: </b>Re: [jboss-as7-dev] Better handling of transaction leaks?<br><br>On 10/19/2011 07:34 PM, Remy Maucherat wrote:<br>> On Wed, 2011-10-19 at 19:29 +0200, Carlo de Wolf wrote:<br>>> On 10/19/2011 04:27 PM, Remy Maucherat wrote:<br>>>> On Wed, 2011-10-19 at 19:25 +0530, Jaikiran Pai wrote:<br>>>>> I agree that there should be a way to easily disable this. The only real<br>>>>> reason why I am in favour of this simple check/cleanup is to ensure that<br>>>>> some rogue application (which doesn't handle transactions correctly)<br>>>>> doesn't end up breaking/affecting some other (well-written) application<br>>>>> deployed on the same instance.<br>>>> A rogue application will be able to trivially do something that would<br>>>> affect other applications in the same instance, I believe.<br>>>><br>>> EE.4.2.2 Transaction in Web Component Life Cycles<br>>> Returning from the service method to the network client with an active<br>>> transaction<br>>> context is an error. The web container is required to detect this error<br>>> and abort the<br>>> transaction.<br>>><br>>> How do you propose we implement this?<br>> I didn't know it was a spec requirement :) Old legacy item, probably. So<br>> you win, congratulations, let's make our product worse.<br>><br>No, we need our product to be the best. It just means we need to have <br>the option to break and bend compliance. Like Jaikiran says, if we can <br>have an easy setting to enable/disable this (preferably in <br>standalone.xml). We're good to go. I would even say to turn the check <br>off by default.<br><br>Carlo<br></blockquote>That's what I have been saying too. It needs to be there for the SPEC, but its really a development/debugging tool, and we can disable it for non-TCK runs (especially performance benchmarking, which is my main concern). I already remove the current valve for all performance tests (EAP 5.x), since I get a good increase in throughput by doing so.<br><br>Andy<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;">_______________________________________________<br>jboss-as7-dev mailing list<br>jboss-as7-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/jboss-as7-dev<br></blockquote><br></div></body></html>