openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chintan4181 <chintan4...@gmail.com>
Subject Re: @Version for sqlserver "timpstamp" datatype
Date Fri, 15 Apr 2011 15:56:25 GMT
Hi Mike,

Currenty Isolation level in Websphere is 4- Repetable Read. Tried with
Serializable (8), but it did not work.

I am trying to simulate the scenario using SOAP UI tool. Multiple threads
are starting parrellaly to update same record. So here i found two
behaviours
If i dont use em.lock(entity, LOCKModeType.OTIMISTIC) (which is deafult),
all threads are updating reocords. No exception is thrown. 

If i use em.lock(entity, LockModeType.OPTIMISTIC_FORCE_INCREMENT), i am
getting lock time out error. 

which level of isolation will help me to solve this issue?

Thanks
Chintan

--
View this message in context: http://openjpa.208410.n2.nabble.com/Version-for-sqlserver-timpstamp-datatype-tp6267241p6276784.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Mime
View raw message