2 Replies Latest reply on Nov 13, 2006 8:40 AM by mcossari

    Transaction locking issue on JBoss 3.2.6 under heavy load in

    rcostanzo

      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

        • 1. Re: Transaction locking issue on JBoss 3.2.6 under heavy loa
          rcostanzo

          One other observation....after seeing the lock contention warnings for a few minutes, that instance receives an EXIT message and leaves the cluster. All of the other boxes then start displaying warnings about discarded NAKACK messages from the locked instance, and then finally the locked instance rejoins the cluster and the locking issue seems to be cleared up. Don't know if this leaving and rejoing the cluster is a symptom or related to the cause....

          • 2. Re: Transaction locking issue on JBoss 3.2.6 under heavy loa
            mcossari

            Hi Robert
            I have the same problem in my server, but, I don't use cluster.
            sometimes, I delete the records from the table jms_messages, and after some time, the problem continues
            how do you solve this problem??

            tks
            marcio