Hi everyone,

Happy New Year to all.

I am facing concurrency issues in my Web App and I used hibernate version to fix it.
It fixed the problem but then application is considerably slowing down to the extent of beoming non-responsive. We have restart the server to fix it.
We have checked the memory consumption, db connection pooling and db locks, everything seems normal but still it becomes non-resposive once or twice evryday.
If I remove the version thing then system is okay but concurrency issue occurs.

Code is as follows:



Technologies used - Spring, Struts 2 , Hibernate with maps
Servers - Webshpere 6.1 and Oracle 10g

Please help me, this is a financial app and I feeling a lot of pressure from my manager.

Regards,
Rajiv

Hi,

I havent tried this before but still i would ask you to refer to the section 11.3.2 and 11.3.3 mentioned in the below link where you can achieve concurrency by using session.saveOUpdate() OR session.flush().You dont have to use optimistic-lock in your mapping attribute if you use either of the option(session.saveORUpdate() OR session.flush()) in your code.

http://docs.jboss.org/hibernate/core/3. ... tions.html

I somehow feel that using optimistic-lock in the Class level is actually locking the entire row in the database which is why it is expensive and it is locking that object till the time it is bounded to the Hibernate Session.But if you use the above two options it will lock the database only when it is actually saving the data in the database and locking time will be reduced by this therby enhancing the scalabality of the application.

Its just my view but you could try doing this and please do let me know your results

-Kartik