Chuck, >From the log, acquireWriteLock timeout after 15 secs because the node lock is >currently owned by a read lock [<clan:3575>:10]. Right before the timeout message, I >can see the read lock owner [<clan:3575>:10] is still active.
Is this the log file the read cache only? Can you again send me the full log file to [EMAIL PROTECTED] FYI, when Rich sent me the log file, I discovered the reason that cache never released the lock was because after a transaction already committed exception, there was still more activities going on. But later on, transaction manager never issues a commit to cache. As a result, cache would hold on to the lock like forever. Thanks, -Ben View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840640#3840640 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3840640 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
