Getting entitymanager delegate causes exception

[nickarls]

When I try setting my extended PC entityManager (Hibernate) to manual flush mode with something like

		Session session = (Session) entityManager.getDelegate();
		session.setFlushMode(FlushMode.MANUAL);

I end up with

javax.ejb.EJBException: Found extended persistence context in SFSB invocation call stack but that cannot be used because the transaction already has a transactional context associated with it.  This can be avoided by changing application code, either eliminate the extended persistence context or the transactional context.  See JPA spec 2.0 section 7.6.3.1.  Scoped persistence unit name=OSTi-3.0.0-SNAPSHOT.war#OSTi, persistence context already in transaction =org.hibernate.ejb.EntityManagerImpl@700ad2e, extended persistence context =ExtendedEntityManager [OSTi-3.0.0-SNAPSHOT.war#OSTi]

10:57:31,154 ERROR [stderr] (http--127.0.0.1-8080-6)           at org.jboss.as.jpa.container.ExtendedEntityManager.getEntityManager(ExtendedEntityManager.java:88)

10:57:31,154 ERROR [stderr] (http--127.0.0.1-8080-6)           at org.jboss.as.jpa.container.AbstractEntityManager.getDelegate(AbstractEntityManager.java:465)

The error message is pretty detailed in what is going on but it worked fine in AS6, has the rule only been inforced recently?. How should setting the manual flush mode be done? I have a feeling that the problem could be in Seam Faces/Persistence that might be doing some transaction-wrapping in the JSF lifecycle...

[nickarls]

Nevermind, I think I got working with a combination of moving to Seam-managed PC:s and updating to Seam Persistence 3.0.1-SNAPSHOT...

[smarlow]

I think we discussed the above on IRC possibly but more recently, AS7-1663 details a problem that could be related.

Was the above for a SFSB with XPC (extended persistence context) invoking another bean with only PC (transactional entity manager)?  Is the SFSB with XPC method running without a JTA transaction? 

[smarlow]

My pull request for AS7 (7.0.2) https://github.com/jbossas/jboss-as/pull/225, eliminates the detailed error message which came from an incorrect check.

[smarlow]

I'm fixing the check, to meet the requirements of 7.6.3.1, which will eliminate the invalid one.  I'm not sure from your description which case you hit.  The new check will cover:

If the component is a stateful session bean to which an extended persistence context has been bound and there is a different persistence context bound to the JTA transaction, an EJBException is thrown by the container.

[smarlow]

Nicklas, never mind, the ExtendedEntityManager error check is correct and that is the one that you got.

[smarlow]

Actually, the ExtendedEntityManager error check doesn't seem right.  Working on a test case...

[smarlow]

Unit test case (https://github.com/scottmarlow/jboss-as/commit/7c7fa408e415ce1bb91963536d83cc0338f75325) passes.