Hi all,

I am facing problem in inconsistent data state with hibernate due to delayed flush().

We are using hibernate and spring in the application.

I have the mapping between three tables:
Class A having multiple instances of class B which in turn has mulitple instances of class C.

When i save class C, i am updating class B and class A also and using saveorupdate method.

Once the save is over, i am using hibernate Query to retrieve the saved instance values and display to the user.

But in one of our testing environments, hibernate is not flushing the changes immediately and this is resulting in inconsistent display issue to the user.

Please suggest me as to how should i resolve this issue..

i tried using session.flush() after the save but still the issue is observed.

Are class B and class A being updated within the same transaction, or in different transactions with different Hibernate sessions? I'd first ensure it was all happening within the same transaction.

All the classes are updated in the same transaction to keep in sync all of them. I am doing session.flush() to manually flush the changes to the database.

this scenario is working fine in my machine but when the same code runs in other environment which is quite loaded, the hibernate is not flushing the changes immediately.

This is resulting in scenario where user updates the values but views the previous values. But after sometime, he is able to view the changes.

I am thinking of following strategies:

1. DO session.refresh() after i re-query the hibernate objects. This may try to get the latest state of the hibernate object.

2. DO session.evict() and sessionFactory.evict() to remove any cached instances.

Please suggest if my strategies are any good. If you have any other suggestion, you are welcome..

Thanks

After a flush you should see the changed values.

Are you using a 2nd level cache?


Use logging to check:
- when and what statements sql statements are issued
- which results are retrieved from the db and which come from the 2nd level cache
- if the 2nd level cache is invalidated apropriatly.


Just to check: You aren't using a new jdbc connection for every call, right?
kind regards.

I had put an interceptor for hibernate events and this is what i am able to observe so far..

1. when i query the hibernate objects through mapping e.g., classAobj.getClassBObjects(), hibernate is firing query to retrieve the ClassB objects as expected.

2. When i change this flow by replacing querying part for ClassB objects by firing a seperate query instead, hibernate is first doing a dirty check on the classA object and then fires the query.

ClassB is mapped as lazy = true collection with ClassA.

So, I am wondering in which instance of the above (i.e., querying through mapping and querying through hsql query) will hit the database and get the latest data...

any useful links will be appreciated.

I know it's been a while, but I am facing that same issue for quite some time now. I basically did all I could to avoid such a scenario. By all I could, I mean hacks. Like security checks if it was really written to the DB. Ridiculously often flush the session. But sometimes a property value is simply not written to the database. Not even delayed. And it mostly happens in heavy load production environment. Locally it doesnt happen at all. It even occurs in unit tests from time to time...

I'm clueless.

Anyone with an idea out there?