Hi,
Done a bit of research on my own and haven't found anything addressing the follow situation.

I have an application that runs on several separate machines, each being it's own separate and independent instance, all having session factories to the same database. I'd like to ensure that all db operations are written to the db asap so that other instances don't get stale data. I understand from the manual that flushing the session does this, but it mentions that unless you explicitly call flush, there's no guarantee when this happens.

Using Spring to get the session factory, an instance of org.springframework.orm.hibernate3.LocalSessionFactoryBean . Also using Spring to get the transaction manager, an instance of org.springframework.orm.hibernate3.HibernateTransactionManager .

Thanks in advance.
-Scott

Hm, I was guessing this was a common situation. Distributed application without clustered hibernate session?

Hi Scott-

Hibernate will flush your changes to the DB when your transaction commits. If you use Spring's transactions, then it happens whenever the transactional method completes.


So if an operation on Machine A commits the txn, the next time Machine B reads from the same table, it will see that new data.

Does that answer your question?

-Adam