Hibernate version: 2.1.8

I'm using Spring in JBoss to manage JTA transactions around my service layer. The problem, I believe, is that the Session isn't being flushed when the JTA is committed, causing all updates to be lost. I can call flush() in my Persistence Managers to work-around this problem. I was hoping setFlushMode(FlushMode.COMMIT) would also fix this, but it doesn't have any effect. I posted to the Spring forum but I thought it might also be an issue with Hibernate not listening for the JTA commit.

Here is the relevant configuration files.

Any help would be appreciated.

I also used to use Spring for Hibernate handling.
But when using JBossAS simply use H3 capabilities (SF.getCurrentSession()) and leave all the rest to JBossAS EJB container (and underlaying Hibernate handling).
I'm doing a whole new portal app with EJB3 and haven't had any problems yet - and the code is much more clean than with Spring's XTransactionManager.
But that doesn't stop you from using Spring.
Check out this: http://wiki.jboss.org/wiki/Wiki.jsp?pag ... ntegration

Rgds, Ales