I wouldn't call this an "issue"; this is exactly the behavior you'd expect when one thread acquires a write lock on a resource and then holds it, while another thread tries to acquire the lock. The 2nd thread times out and throws an exception because the first thread is sleeping with the lock held. If you use transactions, locks are held for the life of the transaction.
If you want this to work, you need to set your LockAcquisitionTimeout to > 15 seconds. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920311#3920311 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920311 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
