The following comment is found in TxCapsule.registerSynchronization() and I believe it is causing a problem in our application.
// OSH: EntitySynchronizationInterceptor bug is fixed long ago, // and since nobody seems to get the warning anymore it should // be safe to be JTA-conformant. // In case of trouble, try changing "true" below to "false". I read in the JTA spec (and the comments mention this also) that the registerSynchronization method should throw a RollbackException if the transaction status is already marked for rollback only. So, I suppose that the implementation is correct as it stands now...however... When my application marks setRollbackOnly, it throws an application exception immediately after doing so. There is nothing in my code that would invoke another bean method, yet the server is making another call to registerSynchronization(), thus causing the improper RollbackException. The object that is registering with registerSynchronization is org.jboss.ejb.GlobalTxEntityMap$GlobalTxEntityMapCleanup. It is causing the register and the subsequent "improper" RollbackException. _________________________________________________________ View thread online: http://main.jboss.org/thread.jsp?forum=66&thread=12171 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
