glassfish
  1. glassfish
  2. GLASSFISH-15903

ConcurrentModificationException observed in the MQ logs during a 24x7 Stress Test RichAccess run

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: v3.0.1, 3.1_b02, 3.1_ms01, 3.1_b03, 3.1_b05, 3.1_b06, 3.1_ms02, 3.1_b07, 3.1_b08, 3.1_b10, 3.1_ms03, 3.1_b12, 3.1_b13, 3.1_b14, 3.1_b15, 3.1_b16, 3.1_ms04, 3.1_b17, 3.1_b18, 3.1_b19, 3.1_b20, 3.1_ms05, 3.1_b21, 3.1_b22, 3.1_b23, 3.1_b24, 3.1_b25, 3.1_b26, 3.1_ms06, 3.1_b27, 3.1_b28, 3.1_b29, 3.1_b30, 3.1_b31, 3.1_b32, 3.1_ms07, 3.1_b33, 3.1_b34, 3.1_b35, 3.1_b36, 3.1_b37, 3.1_b38, 3.1_b39, 3.1_b40, 3.1_b41
    • Fix Version/s: 3.1_b42
    • Component/s: jms
    • Labels:
      None

      Description

      GF Build: Observed with Builds 37 and 40
      Platform: OEL (b37) and Windows 2008 (b40)

      • Observed with RichAccess run (b37) and a RichAccess + SSL run (b40)

      The following Exception appears in the MQ logs on a few instances on each of these runs:
      ******
      [05/Feb/2011:19:32:55 IST] ERROR [B3100]: Unexpected Broker Internal Error : [TransactionLogManager: Checkpoint runnerFailed to synchronize persistence store for transaction log checkpoint]:^M
      java.util.ConcurrentModificationException^M
      at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)^M
      at com.sun.messaging.jmq.jmsserver.persist.file.BaseTransactionManager.writePreparedTransactionsToPreparedTxnStoreOnCheckpoint(BaseTransactionManager.java:244)^M
      at com.sun.messaging.jmq.jmsserver.persist.file.TransactionLogManager.doCheckpoint(TransactionLogManager.java:828)^M
      at com.sun.messaging.jmq.jmsserver.persist.file.CheckpointManager.run(CheckpointManager.java:74)^M
      at java.lang.Thread.run(Thread.java:662)^M
      *****

      The Exception does not seem to cause any harm to the test.

        Activity

        Hide
        amyk added a comment -

        So your previous comment "a similar but different stack trace seems to have been fixed by Amy in http://java.net/jira/browse/MQ-73 on 5th Jan" was really referring to the one from broker log for MQ-72 which was created on Jan 03 using a MQ build before build24. Then that's the same one that has been fixed by MQ-73 (MQ build24-c).

        Show
        amyk added a comment - So your previous comment "a similar but different stack trace seems to have been fixed by Amy in http://java.net/jira/browse/MQ-73 on 5th Jan" was really referring to the one from broker log for MQ-72 which was created on Jan 03 using a MQ build before build24. Then that's the same one that has been fixed by MQ-73 (MQ build24-c).
        Hide
        Chris Kasso added a comment -

        Approved for RC3.

        Show
        Chris Kasso added a comment - Approved for RC3.
        Hide
        varunrupela added a comment -

        Answer is Yes to Amy's Comment.

        Show
        varunrupela added a comment - Answer is Yes to Amy's Comment.
        Hide
        amyk added a comment -

        fixed in MQ build29-b (7018423) and integrated to GlassFish 3.1 for RC3 build (b42)

        Show
        amyk added a comment - fixed in MQ build29-b (7018423) and integrated to GlassFish 3.1 for RC3 build (b42)
        Hide
        amyk added a comment -

        updated Affects Versions

        Show
        amyk added a comment - updated Affects Versions

          People

          • Assignee:
            amyk
            Reporter:
            varunrupela
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: