I'm using hibernate in a multiuser environment. This means, many users are able to update an object on the database at the same time using different (hibernate) sessions.

My problem is, that an object o, that was once loaded from the db, is cached and not reloaded from db, until I force this by an explicit session.reload(o). This means, if o belongs to a result of a session.find() it's not reloaded, even if the database tupel, that belongs to o, was updated and committed by another session. So the session, that uses the find(), doesn't get the actual persistent state of o.

What I need, is a mechanism, that forces the find() command, to reload object o, when the database tupel has been changed between session.load() and session.find().

Any idea? Thanks in advance.

If you are not doing evil things like using a long-running session, all that this behaviour does is helps enforce transaction isolation.


If you are using long-running sessions then STOP :)

Thanks for the quick response.

But I'm not sure, I understand, how transaction isolation would help me in this case? Could you give me more details?

By the way, I found session.clear() in hibernate 2.1. If I use this before the session.find() statement, it solves my problem. Do I get any disadvantages by using session.clear() before every session.find() statement?

Your clearing the session cache hence it has to hit the database to get the objects which sounds like your using long running sessions to me. Disadvantage is a drop in potential performance due to forced cache flushes. In reality this has a bit of a smell and I would reconsider the architecture you are using.