<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">You should actually be checking for more states than just ACTIVE (e.g. it could be MARKED_ROLLBACK).<div><br></div><div>Anything other than UNKOWN or NO_TRANSACTION I think.</div><div><br></div><div>Stuart<br><div><br></div><div><br></div><div><br><div><div>On 29/11/2011, at 8:15 AM, Nicklas Karlsson wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Sure, it's just something like
<a href="http://pastebin.com/7ZBMcYkG">http://pastebin.com/7ZBMcYkG</a> <br><br><div class="gmail_quote">On Mon, Nov 28, 2011 at 11:11 PM, Shane Bryzak <span dir="ltr"><<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div text="#000000" bgcolor="#FFFFFF">
Would you mind sharing that with us Nick? :)<div><div class="h5"><br>
<br>
On 29/11/11 07:08, Nicklas Karlsson wrote:
<blockquote type="cite">Like I commented in the JIRA, I think I also had this
issue and Stuart recommended this simple rollback filter which I
currently use and appear to have solved the issue.<br>
<br>
<div class="gmail_quote">On Mon, Nov 28, 2011 at 11:03 PM, Shane
Bryzak <span dir="ltr"><<a href="mailto:sbryzak@redhat.com" target="_blank">sbryzak@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So it looks
like the filter idea is what Jason and Lincoln have come up<br>
with also. Jason, how long would this take to implement?<br>
<div>
<div><br>
On 29/11/11 07:02, Stuart Douglas wrote:<br>
> This looks like a transaction leak, not sure where
from.<br>
><br>
> EE app servers are supposed to have a mechanism in
place to detect and rollback leaking transactions from a
web request. AS 7.0 was missing this, however I added it
for the 7.1 Beta release.<br>
><br>
> For 7.0 I think the only real solution is to either
figure out where the TX leak is coming from, or write a
filter that detects transaction leaks and rolls back.<br>
><br>
> Stuart<br>
><br>
><br>
> On 29/11/2011, at 7:54 AM, Shane Bryzak wrote:<br>
><br>
>> Has someone consulted Stuart about this issue?<br>
>><br>
>> On 29/11/11 03:29, Jason Porter wrote:<br>
>>> That may work. If the steps are relatively
small to recreate it.<br>
>>><br>
>>> Sent from my iPhone<br>
>>><br>
>>> On Nov 28, 2011, at 10:16, Cody Lerum<<a href="mailto:cody.lerum@gmail.com" target="_blank">cody.lerum@gmail.com</a>>
wrote:<br>
>>><br>
>>>> I don't have a test for it, and I don't
think I will have the time to<br>
>>>> learn how to repo it in arq anytime soon.
I can branch my seam-crm<br>
>>>> project to create an easy repo if someone
can craft a test based on<br>
>>>> that.<br>
>>>><br>
>>>> -C<br>
>>>><br>
>>>> On Mon, Nov 28, 2011 at 10:12 AM, Jason
Porter<<a href="mailto:lightguard.jp@gmail.com" target="_blank">lightguard.jp@gmail.com</a>>
wrote:<br>
>>>>> Cody, do you have an arquillian test
that reproduces this? This is a pretty big one and I don't
want to say this is fixed without a test demonstrating
this is fixed.<br>
>>>>><br>
>>>>> Sent from my iPhone<br>
>>>>><br>
>>>>> On Nov 28, 2011, at 9:24, Cody
Lerum<<a href="mailto:cody.lerum@gmail.com" target="_blank">cody.lerum@gmail.com</a>>
wrote:<br>
>>>>><br>
>>>>>> FWIW I think we should hold off
on a CR1 release until<br>
>>>>>> <a href="https://issues.jboss.org/browse/SEAM-99" target="_blank">https://issues.jboss.org/browse/SEAM-99</a>
can be resolved.<br>
>>>>>><br>
>>>>>> -C<br>
>>>>>><br>
>>>>>> On Sun, Nov 27, 2011 at 7:26 PM,
Shane Bryzak<<a href="mailto:sbryzak@redhat.com" target="_blank">sbryzak@redhat.com</a>>
wrote:<br>
>>>>>>> Hi everyone,<br>
>>>>>>><br>
>>>>>>> We are gearing up release
Seam 3.1.0.CR1 in a couple of days. Currently we<br>
>>>>>>> have 56 open issues [1], I'll
probably be bumping many of these but if you<br>
>>>>>>> are able to help out by
fixing one or two of these then it would be much<br>
>>>>>>> appreciated. I'll probably
start the release on Wednesday evening my time<br>
>>>>>>> (+10GMT), so we'll need to
have a code freeze by then.<br>
>>>>>>><br>
>>>>>>> Thanks,<br>
>>>>>>> Shane<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> [1]<br>
>>>>>>> <a href="https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=12314291" target="_blank">https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=12314291</a><br>
>>>>>>>
_______________________________________________<br>
>>>>>>> seam-dev mailing list<br>
>>>>>>> <a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
>>>>>>> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>
_______________________________________________<br>
>>>>>> seam-dev mailing list<br>
>>>>>> <a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
>>>>>> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
>> _______________________________________________<br>
>> seam-dev mailing list<br>
>> <a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
---<br>
Nik<br>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>---<br>Nik<br>
</blockquote></div><br></div></div></body></html>