[jboss-jira] [JBoss JIRA] (WFLY-1810) SFSB tx lock not released in exception was thrown in Synchronization callback

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795510#comment-12795510 ] 

RH Bugzilla Integration commented on WFLY-1810:
-----------------------------------------------

Ladislav Thon <lthon at redhat.com> made a comment on [bug 990102|https://bugzilla.redhat.com/show_bug.cgi?id=990102]

Doh! I'm sorry, I incidentally used pure 6.1.1.ER4 without the fix in the build from comment 10.

I did another run, this time with the fix for real, but the problem persists. See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-2clusters-ejbremote-shutdown-repl-async-timeout-investigation/14/
                
> SFSB tx lock not released in exception was thrown in Synchronization callback
> -----------------------------------------------------------------------------
>
>                 Key: WFLY-1810
>                 URL: https://issues.jboss.org/browse/WFLY-1810
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 8.0.0.Alpha1
>            Reporter: Paul Ferraro
>            Assignee: jaikiran pai
>             Fix For: 8.0.0.Alpha4
>
>
> Because the owning tx was never pushed into the OwnableReentrantLock ownership stack in org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.handleThrowableInTxSync(...).
> This will cause subsequent Lock.tryAcquire(..) to fail for a different tx.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira