I have a use case where a column (not key) value may get updated by another application and i want hibernate to see the change. Unfortunately every time i execute the query i always get the old column value.

I'm opening and closing a session every time so it can't be the session cache. I've turned off query and second level cache. I've called session.refresh on the return object. Nothing worked and i'm running out of ideas.

Any ideas would be great.
Thanks.

I've found a workaround on this thread where if i do the following just after the query execution the value is refreshed:



So doing a refresh doesn't work but starting a dummy transaction just before doing the refresh works ???
Is there any explanation for this and a more elegant way to solve the problem ?

Which transaction isolation level are you using? From your description it seems like it could be TRANSACTION_REPEATABLE_READ, which means that once you have started your transaction, you will no longer see updates that are made in other transactions. This may be why starting a dummy transaction works as a workaround, since that sets a new starting point for the "repeatable" reads.

You may try setting the 'hibernate.connection.isolation' configuration value. See http://www.hibernate.org/hib_docs/v3/re ... ional.html for more information. I think TRANSACTION_REPEATABLE_READ=4 and TRANSACTION_READ_COMMITTED=2

Setting hibernate.connection.isolation to 2 worked great.
Many thanks.