Derby
  1. Derby
  2. DERBY-5394

Reduce chance of OOME with XAMemTest.testDerby4137_TransactionTimeoutSpecifiedNotExceeded in low memory suite

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.9.1.0
    • Fix Version/s: 10.8.2.2, 10.9.1.0
    • Component/s: Test
    • Labels:
      None

      Description

      See thread on derby-dev: "Problems with junit-lowmem" (29th of August 2011).

      The test XAMemTest.testDerby4137_TransactionTimeoutSpecifiedNotExceeded doesn't release all the memory it uses and causes either excessive GC activity (and a much longer run time) or an OOME.

        Issue Links

          Activity

          Hide
          Kristian Waagan added a comment -

          Attaching patch 1a, which makes the XAMemTest be executed last in the low-mem suite.

          I've observed a runtime of 46 and 22 minutes for the low-mem suite. It now dropped (back) to around 12 minutes.

          Committed to trunk with revision 1162737.

          Show
          Kristian Waagan added a comment - Attaching patch 1a, which makes the XAMemTest be executed last in the low-mem suite. I've observed a runtime of 46 and 22 minutes for the low-mem suite. It now dropped (back) to around 12 minutes. Committed to trunk with revision 1162737.
          Hide
          Kristian Waagan added a comment -

          Merged fix to the 10.8 branch, hoping there will be another RC.

          I don't plan to do more on this issue now, but for later, and maybe for similar cases, it should be investigated if using a decorator that shuts down the database (and possibly then engine?) addresses the problem.

          Show
          Kristian Waagan added a comment - Merged fix to the 10.8 branch, hoping there will be another RC. I don't plan to do more on this issue now, but for later, and maybe for similar cases, it should be investigated if using a decorator that shuts down the database (and possibly then engine?) addresses the problem.
          Hide
          Kristian Waagan added a comment -

          Closing issue, no issues seen after the fix was applied.
          The fix committed under this issue was a work-around, not a proper fix addressing the general root cause.

          Show
          Kristian Waagan added a comment - Closing issue, no issues seen after the fix was applied. The fix committed under this issue was a work-around, not a proper fix addressing the general root cause.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development