EntityManager auto flush not performed?

[zergspirit]

Hi.

We're having a strange little problem.
We're developing an application which is working perfectly in our development environment, but we have witnessed a strange difference between our development environment and production one, although we have the exact same configuration regarding persistence (and everything, basically).
- Jboss 4.2.3
- Postgres data base
- Seam 2.1.1.GA
The only real difference we have is that in production, Jboss and Postgres are running on the same host.

The problem is basically that when we create/modify data, we need to flush() our entityManager (always a SMPC) whereas we do not need it in our development environment. Strange thing is that it's not needed in every of those methods, though I can't think of anything they would have in common.
It might be some configuration we forgot somewhere, but we clearly don't see where.

Sorry that I'm not being more specific, but I don't see anything you should know about this, but let me know if you need something else.

[arshadm]

Hi,

Sounds like somewhere in the code the entity manager is being modified to manual flush mode.

I would like check if any code uses flush mode manual, the setting in components.xml and all pages.xml to check to ensure nobody has done a begin conversation with manual flush mode.

Are you dependent on any jars with components that might modify the flush mode?

Regards.

[zergspirit]

Hmm I don't think it's possible since we have the same code in development and production environment.

[gonorrhea]

In JPA 1.0 and 2.0 there are two flush modes (AUTO and COMMIT).  MANUAL flush mode is a Hibernate extension.

If you need to write em.flush() to synchronize PC changes with db, then most likely you have MANUAL flush mode enabled somehow...