SaveorUpdate syncronisation

praveen_kumar0505 · **Joined:** Sun Oct 26, 2008 5:49 pm **Posts:** 6

Hello ,

i am currently working with hibernate3.3

in our code we load the session obj from the config (no spring support) ... and keep this in the ThreadLocal.

Our app is a multiThreaded application . On a request we create a new thread and call saveorupdate by getting the session from the threadlocal ....

i am currently getting a DUPLICATE_KEY exception when i call this method simultaneously from 2 thread .... i have flushed the session and also made a commit, but looks like before i flush the 2nd thread fires the update and i get into this issue.

Any thoughts on this will is highly appreciated.

regards
Praveen

gonzao_diaz · **Joined:** Mon Nov 26, 2007 2:29 pm **Posts:** 443

Hibernate basically doesn't have a way to handle this (aside from versions and optimistic locking), it piggybacks on the transaction management system your database has.
Either manipulate your locking parameters, or add thread sychronization code on your application.

praveen_kumar0505 · **Joined:** Sun Oct 26, 2008 5:49 pm **Posts:** 6

Thanks Gonzo,

i have added a locking on my session object since i suspected the same session object was getting used for the two transactions, but seems like thats not the case and the issue wasnt resolved,

As far as i think i will need to syncronize on the object itself now.. but that will be a bigger penality on performance and i dont want to go in that direction.

gonzao_diaz · **Joined:** Mon Nov 26, 2007 2:29 pm **Posts:** 443

My name is Gonzalo.

If you don't want to add synchronization code, then you will have to tune your DB to accept concurrent updates. Hibernate sessions don't handle concurrent access.

praveen_kumar0505 · **Joined:** Sun Oct 26, 2008 5:49 pm **Posts:** 6

Sorry.. for the name thing..

well.. i think i need to do some more RnD on to how can update fire an insert .. when i have the data in the DB .... thats whats bugging me.