Transaction trouble

[grimesp]

Somehow my FlushMode is being set to NEVER in my application. I have no idea where, I have greped, searched in my IDE, etc. I took Loren's advice and explicitly set the FlushMode to AUTO in all of my save methods. This fixed one of my 5 save methods, that one now persists to the database. The other save methods no longer throw the "Write operations are not allowed in read-only mode (FlushMode.NEVER)...", they appear to do the same thing as the save method that actually works but nothing is persisted to the database.

Any ideas?

[cosmin]

I had problems with 7.3 . Don't remember the driver version , as i simply took the latest for my DB . You seem up to date so I guess no luck with findinig the problem there

[ponticello]

I was having the same problem with an Oracle db.

InvalidDataAccessApiUsageException: Write operations are not allowed in read-only mode (FlushMode.NEVER) - turn your Session ...

I believe the problem was caused by upgrading to the latest 3.1 Hibernate jar, but that's just a guess.

I added flushMode property to openSessionInViewInterceptor everything seems to work.

<bean name="openSessionInViewInterceptor"
class="org.springframework.orm.hibernate3.support. OpenSessionInViewInterceptor">
<property name="sessionFactory"><ref bean="sessionFactory"/></property>
<property name="flushMode">
<bean id="org.springframework.orm.hibernate3.HibernateAc cessor.FLUSH_AUTO" class="org.springframework.beans.factory.config.Fi eldRetrievingFactoryBean"/>
</property>
</bean>

I hope this helps.

[xml2008]

I am also using OpenSessionInViewFilter. When I using the old transaction config
method, every thing is OK. But when I converted the config to use the new tx:advice style, the same problem accurred.

I have solved the problem with a customized OpenSessionInViewFilter implementation as the following code shows:

public class OpenSessionInViewFilter extends org.springframework.orm.hibernate3.support.OpenSes sionInViewFilter {
protected Session getSession(SessionFactory sessionFactory) throws DataAccessResourceFailureException {
Session session = SessionFactoryUtils.getSession(sessionFactory, true);
session.setFlushMode(FlushMode.AUTO);
return session;
}

protected void closeSession(Session session, SessionFactory sessionFactory) {
session.flush();
SessionFactoryUtils.releaseSession(session, sessionFactory);
}
}

[Costin Leau]

Can you please raise an issue on JIRA? Thanks.

[grimesp]

xml2008, thanks so much for the post. I don't know why I didn't go directly to the srouce and the source documentation in the first place. It would have saved me lots of pain.

From the documentation for OpenSessionInViewFilter:

NOTE: This filter will by default not flush the Hibernate Session, as it assumes to be used in combination with service layer transactions that care for the flushing, or HibernateAccessors with flushMode FLUSH_EAGER. If you want this filter to flush after completed request processing, override closeSession and invoke flush on the Session before closing it. Additionally, you will also need to override getSession() to return a Session in a flush mode other than the default FlushMode.NEVER. Note that getSession and closeSession will just be invoked in single session mode!

So in conclusion, Spring was setting the flush mode to NEVER!

To fix my problem I did as the documentation suggests and as xml2008 suggested and over-rode the getSession() and closeSession() methods in OpenSessionInViewFilter.

Thanks for all the help.

[Costin Leau]

OSIV deliberately sets flush mode to NEVER - it should be used along with a TransactionManager. The problem is that using tx:advice does not trigger the flush.

[grimesp]

I am not using tx:advice. I am using declarative transactions with the HibernateTransactionManager and there is no flush triggered.

[hasdy]

This helped quite a bit... thanks