Hi,
 While using PESSIMISTIC locking approach with JBossCache1.2 and Hibernate2.1.3 
in our application, in JBoss-3.2.3, we frequently see the following exceptions:

10:16:29,999 ERROR [IdentityLock] write lock for 
//com/dbdata/measureeditor/hibernateobject/MsMeasure/[EMAIL PROTECTED]: 
=101,versionId: =1] could not be acquired after 15000 ms. Lock map ownership 
Read lock owners: [<null>:5]
  | Write lock owner: <null>:3
  |  (caller=<null>:4)

In the treecache.xml we have specified the value for LockAcquisitionTimeout 
attribute as 15000. 

My question is, does increasing this attribute to a very high value(say 400000) 
have any adverse effects on the application?   

Thank you.




View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3908129#3908129

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3908129


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to