[jboss-jira] [JBoss JIRA] (AS7-268) SFSB isn't disassociated from a transaction

[ https://issues.jboss.org/browse/AS7-268?page=com.atlassian.jira.plugin.sy... ] Laszlo Miklosik commented on AS7-268: ------------------------------------- Were there code changes made for this issue? I am having similar problems with JBoss 7.0.2 while using a SFSB with BMT. Sometimes I am getting: {code} javax.ejb.EJBException: EJB 3.1 FR 4.6 Stateful instance org.jboss.as.ejb3.component.stateful.StatefulSessionComponentInstance@7067ba82 is already associated with tx 0:ffff7f000101:628fc41c:4f466b0d:c9 (current tx null) {code} (null tx) other times: {code} javax.ejb.EJBException: EJB 3.1 FR 4.6 Stateful instance org.jboss.as.ejb3.component.stateful.StatefulSessionComponentInstance@6c48d880 is already associated with tx 0:ffff7f000101:541d5a8c:4f465ea4:1241 (current tx 0:ffff7f000101:541d5a8c:4f465ea4:137a) {code} (non null tx) while calling a method like: {code} public void startTx() throws SystemException, NotSupportedException { if (ctx.getUserTransaction().getStatus() == Status.STATUS_NO_TRANSACTION) { ctx.getUserTransaction().begin(); } } {code} because StatefulSessionSynchronizationInterceptor line {code} // get the key to current transaction associated with this thread currentTransactionKey = transactionSynchronizationRegistry.getTransactionKey(); {code} sometimes returns a transaction even if there is none started for the given SFSB instance, at least this is what {code} ctx.getUserTransaction().getStatus() == Status.STATUS_NO_TRANSACTION {code} means. Note: the problem can be easily reproduced if the above described startTx() method is called many times one after the other. Thanks, Laszlo Miklosik -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira