mq
  1. mq
  2. MQ-72

newTxnLog enabled broker generates a really large MQ 'txnlog' file for long running transacted client

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.4u1, 4.4u2, 4.5
    • Fix Version/s: 4.5
    • Component/s: broker-core
    • Labels:
      None

      Description

      This is reported by GlassFish QE on GlassFish 3.1 stress test (RichAccess):
      "The run is generating a really large MQ transaction log - of the order of a few tens of GB over a period of a few days. Below is a list of the largest files on one of the instances where the size hit ~45 GB (in 10 days).
      45379411901 ./glassfish3/glassfish/nodes/agent4/instance103/imq/instances/stclusterinstance103/fs370/txnlog
      ......

        Issue Links

          Activity

          Hide
          amyk added a comment -

          cpSize in txnlog writer became negative when max size < cpOffset, bug 7010372 is filed and fixed in 4.5build24

          Show
          amyk added a comment - cpSize in txnlog writer became negative when max size < cpOffset, bug 7010372 is filed and fixed in 4.5build24
          Hide
          varunrupela added a comment -

          This issue has been verified as fixed with GF nightly build 37 from 10th Jan.

          Show
          varunrupela added a comment - This issue has been verified as fixed with GF nightly build 37 from 10th Jan.
          Hide
          amyk added a comment -

          close the issue as the fix has been verified

          Show
          amyk added a comment - close the issue as the fix has been verified

            People

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

              Dates

              • Created:
                Updated:
                Resolved: