Hi, I am running JBoss 3.2.6 in a 5 instance cluster. I am using the container configuration cmp2.x jdbc2 pm with cache invalidation. I am NOT doing any HTTP session replication. When my servers are under heavy load, I experience the following issue:
One instance will start logging errors like: WARN [org.jboss.tm.TransactionImpl] Transaction TransactionImpl:XidImpl [FormatId=257, GlobalId=mateso-webapp3//16199095, BranchQual=] timed out. status=STATUS_ACTIVE WARN [org.jboss.tm.TransactionImpl] Lock contention, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=mateso-webapp3//16199095, BranchQual=] and become locked up. Subsequently, all of the other 4 instances in my cluster become locked up. I have to kill the instance that the locking issue originated on for all of the other instances to start working properly again. I have checked our Oracle database and there are no waiting queries when this happens, which points to it not being a database locking issue. What other possibilities are there which would cause all members of the cluster to lock? I had thought that cache invalidation was asynchronous, but if it was synchronous then that could explain it. Also, is there a way to track down what the transaction warnings above are locking on? Thanks. -Rob View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3889581#3889581 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3889581 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
