Why does a Fetch / get / query throw OptimisticLockException

bubba.hibernate · **Joined:** Mon Mar 21, 2011 3:40 pm **Posts:** 10

I'm working with JPA 1.99 and Optimistic Concurrency.

I have versioned entities, and am fetching/locking/merging them as needed.

My question is: Why does the retrieval throw an optimisticLockException? I would think it wouldn't throw until it tries to merge/persist the the entity.

-JD

bubba.hibernate · **Joined:** Mon Mar 21, 2011 3:40 pm **Posts:** 10

Continuing to debug this...
I notice that a select is doing an update for some reason...

So.. Insert EntityVersion =0;

Fetch... Does a select, and then an Update to version 1.

Doesn't seem right to me.

bubba.hibernate · **Joined:** Mon Mar 21, 2011 3:40 pm **Posts:** 10

Closing in on this issue I think I know generally what it is now...

My entity has a couple Custom User Types to Support double[] array's and int[] arrays

I think the User Type or some other part of Hibernate thinks that they are always modified... and so after the Select it automatically does an Update...

For similar reasons this is exploding all my optimistic concurrency code.

bubba.hibernate · **Joined:** Mon Mar 21, 2011 3:40 pm **Posts:** 10

Audit Columns... Oh audit .. why did I have to be so clever.... The trigger of course changes the modified date on insert...

Problem solved.

sanne.grinovero · **Posted:** Sun Mar 27, 2011 6:52 pm

Nice one :)
What's JPA 1.99 by the way?