"[EMAIL PROTECTED]" wrote : By 'coordinator' I *didn't* mean the JGroups coordinator, but the coordinator of the 2-phase-commit protocol, so the member on which a TX.commit() was called. | 1.3. will be released in Feb/March 2006. | In the meantime you have to call TreeCache.releaseAllLocks(String fqn). |
Ok, I understand. But wiil releaseAllLocks call be safe? E.g., if evict method of eviction policy is called - is there any garantee, that this node is not locked by active cluster node? If not - I can't call releaseAllLocks, because I can remove locks during open transaction, which is dangerous. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3909000#3909000 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3909000 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
