Using toplink running in oc4j in 11.1.1.0.0

Question

Hi,
I'm using Toplink 11g Release 1 (11.1.1.0.0) (Build 070624) in a web app running in oc4j. I've noticed that sometimes my changes do not get flushed to the database despite the fact that I see the update and commit in toplink logging. The app does correctly see the changes when queried from multiple sessions, yet the changes are not in the db. Do you know where the changes are being cached and how I can flush them to the db?
When I startup oc4j, all data in the table disappears. This may be due to something that someone else in our team is doing when oc4j starts up, but I haven't been able to find out what it is yet.
I don't think these are toplink issues, but I am hoping you might be able shed some light on this.
Thanks,
Vicki

Answer 1

Jim was spot on. As he suggested, I put in a check to see if the object I was updating was the same as the shared copy in the cache from the ServerSession and indeed it was.
I was querying my object and using SessionFactory.detach() to make a copy. However, I was then hanging onto a copy of my object after doing a uow.deepMergeClone() and uow.commit() and this working copy seems to become the shared copy. So when I made more changes to the object, I was corrupting my session cache.
The other unrelated problem of data being deleted when starting up oc4j was indeed some code in our app being called inadvertantly when initialized our app.