[jboss-jira] [JBoss JIRA] (WFLY-3731) org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor should not register a Synchronization if the transaction was rolled back
Carlo de Wolf (JIRA)
issues at jboss.org
Fri Sep 5 06:41:00 EDT 2014
[ https://issues.jboss.org/browse/WFLY-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlo de Wolf reopened WFLY-3731:
---------------------------------
> org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor should not register a Synchronization if the transaction was rolled back
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3731
> URL: https://issues.jboss.org/browse/WFLY-3731
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: JBoss AS7 7.2.0.Final, 8.0.0.Final, 8.1.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Fix For: 8.2.0.CR1, 9.0.0.CR1
>
>
> http://fpaste.org/125252/ shows what happens when the transaction has already been rolled back ().
> {quote}
> WFLYEJB0458: Failure in caller transaction.: java.lang.IllegalStateException: No transaction is running
> at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple.getTransactionImple(TransactionSynchronizationRegistryImple.java:228)
> {quote}
> Test case is available via https://github.com/scottmarlow/wildfly/tree/transactiontimeout_clientut
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the jboss-jira
mailing list