So I'm working in Jboss EAP1, so the version of hibernate may be a little old. If this has been fixed subsequently, just let me know. I'm dealing with EJB3.1 mostly, but have slipped into hibernate specifics where necessary to get the extra performance necessary to get work done.

I'm working on a very large enterprise software which uses very very nested behaviour logic inside EJB's which run for several seconds. During this time, arbitrary sets of entites are fetched into the code from the DB. Over several permutations of performance work, I've attempted detaching, selective flushing with commit mode, etc.. to improve hibernate performance. For the most part, its been successful, but to avoid exceedingly long flush operations, I've recently defaulted basically all DB fetches as read-only.



Inside the flush code, it finds a EntityEntry for myEntry (since its detached but styill resident) but since it was flagged as read-only before being detached, the entity's change doesn't get persisted back to the DB because the flush listener doesn't think anything's changed (because it was flagged as read-only prior).

Note, my 'solution' to the problem was to purge the entity's key EntryEntry from the persistence context immediately before adding it back in, which makes everything work, though a little more klunky than it should've been. I wish I know why this behaviour was occuring. Ideally when an entity is detached, it should be setting the entry writable again, or at least ignoring the status when detecting that the entity is detached?