Old data is read after Transaction.comit()

Tan4ik · **Joined:** Fri Jun 03, 2005 4:42 am **Posts:** 4

After the code

Code:

    Session hs = getSession();
    Transaction tx = hs.beginTransaction();
    hs.saveOrUpdate(bean);
    tx.commit();

a new thread is started and sometimes reads old value of bean.

How can I be sure that data in database is already updated?

dirkschmidt · **Posted:** Fri Jun 03, 2005 9:29 am

try session.flush() to synchronize session cache with db or session.evict(bean) to remove bean from session cache (and force reload).

Tan4ik · **Joined:** Fri Jun 03, 2005 4:42 am **Posts:** 4

dirkschmidt wrote:

try session.flush() to synchronize session cache with db or session.evict(bean) to remove bean from session cache (and force reload).

Session has COMMIT flushMode and bean changes are successfully transfered into database. The problem in second thread that was started after commit and has already read old value of bean before the database updating.
The question is "How to stop execution until the data will be transfered into database?"

ramnath · **Posted:** Fri Jun 03, 2005 9:47 am

Hi

Try using a LOCK

Tan4ik · **Joined:** Fri Jun 03, 2005 4:42 am **Posts:** 4

ramnath wrote:

Try using a LOCK

Can you give some example? We can't lock object along with reading.

lqycfnd · **Posted:** Fri Jun 03, 2005 10:32 am

Have you tried

Session.refresh(object).

This refreshes the saved object with new values so you don't have to read it again.

Tan4ik · **Joined:** Fri Jun 03, 2005 4:42 am **Posts:** 4

lqycfnd wrote:

Have you tried

Session.refresh(object).

This refreshes the saved object with new values so you don't have to read it again.

How should the second thread guess that it should call Session.refresh(object)? And when should it do that?