Please forgive my ignorance, but I would like to understand what is happening when the TreeCache LRU eviction thread runs in a REPL_SYNC mode.
Please confirm, the eviction thread DOES NOT use the transaction manager at all, either for reading or writing. The eviction thread does not execute in the context of a JTA transaction. As you can see from the logs I posted the "write lock could not be acquired" error is logged on the same thread (Thread-31) as eviction policy is running on. This means the eviction thread is trying to establish some lock. I just assumed this was a transaction lock, but it must be some internal locking mechanism on the local node only. Please confirm this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3942926#3942926 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3942926 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
