Hello all,

My app does the following:-

1. Starts a transaction
2. It needs to perform an operation until a positive result is obtained.
3. The operation goes like, retrieve data from the data, perform checks and delete some of the data
4. At the start of every iteration I go to the database to fetch data, and during one of those fetches I get a StaleStateException

Can anyone suggest a way forward please?

Cheers
Gokul

Hello Gokul,
Here are my thoughts:- you need to understand why you are getting the StaleObjectException in order to get around with it.
In my experience in our app here is one of the scenario where I have encountered the StaleObectException. I'm not sure but the guess is that you are having the same issue.
Parent Object having Set/List of children and making changes to the children automatically triggers to flag the Parent Object as "Dirty" and needs to be synced to the database. So saving the Parent and get the re-synced object of the Parent is important.
For example:- Instance Cat has Set of Kitten objects and making changes to the Kitten Objects makes the Version column(Version column or some flag in your app to store the state of the object by Hibernate) on the Cat to get bumped up.Saving the Cat is the right thing to do but you need to get the Cat instance again from the database.
Cat c .. Version 1
getKittens..
deleteKitten
updateKitten
Save Cat The state of the Kittens is updated and Cat gets the Version 2 in the database.
cat.getkittens -- Will cause Hibernate to throw StaleObjectException since Hibernate has an issue with the State of the cat. Get the instance of the Cat again from the database. Nothing has technically changed except for the State(or the Version column) on the object.
Get the Cat from db and then cat.getKittens to avoid the StaleObjectException.

Hope this helps,
Srilatha.