[jboss-jira] [JBoss JIRA] (WFLY-3730) JPA container should check for STATUS_ROLLEDBACK

[Scott Marlow (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Marlow resolved WFLY-3730.
--------------------------------

    Fix Version/s:     (was: 9.0.0.CR1)
                       (was: 8.2.0.CR1)
       Resolution: Won't Fix


It doesn't make sense to check the transaction status for rolled back as the next thing we will do, is create a new persistence context which will fail with the same "no transaction" error.

> JPA container should check for STATUS_ROLLEDBACK
> ------------------------------------------------
>
>                 Key: WFLY-3730
>                 URL: https://issues.jboss.org/browse/WFLY-3730
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JPA / Hibernate
>    Affects Versions: JBoss AS7 7.2.0.Final, 8.0.0.Final, 8.1.0.Final
>            Reporter: Scott Marlow
>            Assignee: Scott Marlow
>
> See ISE thrown in http://fpaste.org/125260.
> Also see test case on https://github.com/scottmarlow/wildfly/tree/transactiontimeout_clientut
> A related concern is shown in http://fpaste.org/125252 which comes from org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)