On 08/14/2014 11:59 AM, Steve Ebersole wrote: > Well it *should* mean that the EM in question was created outside the > scope of a transaction. The JPA spec says that in cases of an > application-managed PC where the EM is created outside the scope of the > JTA txn, the provider should not automatically join the EM to any JTA > txn later implicitly. Instead the expectation is for the application to > explicitly join the EM to the transaction via the EM.joinTransaction method: > > <quote> > When a JTA application-managed entity manager is used, if the entity > manager is created outside the > scope of the current JTA transaction, it is the responsibility of the > application to join the entity manager > to the transaction (if desired) by calling > EntityManager.joinTransaction. If the entity man- > ager is created outside the scope of a JTA transaction, it is not joined > to the transaction unless Entity- > Manager.joinTransaction is called. > </quote> > > Note this behavior was made somewhat controllable in JPA 2.1 with the > introduction of SynchronizationType. > > I'd have to refresh my memory on the expectation here wrt > container-managed PCs. So that would be my first question to you of the > situation... Is this a app or container managed PC? > > It is odd that they see a "local database transaction" instead though. > You sure this isn't a series of auto-commit transactions?
I won't be sure until they enable TRACE logging for org.jboss.as.jpa and give us more logs. I'm waiting for that. > > > > > On Thu, Aug 14, 2014 at 10:23 AM, Scott Marlow <smar...@redhat.com > <mailto:smar...@redhat.com>> wrote: > > I'm trying to help a user [1] that is complaining that a local database > transaction is used, instead of the JTA transaction as they expect. I > asked them to enable TRACE logging for { org.jboss.jca, org.hibernate, > org.jboss.as.jpa + com.arjuna} and see the "Skipping JTA sync > registration due to auto join checking" log message. > > What does the "skipping JTA sync registration due to auto join checking" > mean exactly? [2] shows a small example of the log output with an > active JTA transaction in use. > > Scott > > > [1] https://issues.jboss.org/browse/WFLY-3619 XA END / un-enlist for > database connection called to early > > [2] http://fpaste.org/125603/80296401/ > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org <mailto:hibernate-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/hibernate-dev > > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
