Uploaded image for project: 'Daffodil'
  1. Daffodil
  2. DAFFODIL-1862

Better logging/reset mechanism for MarkPool

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.0
    • Component/s: Back End
    • Labels:
      None

      Description

      It is possible for MarkPool instances to leak, which often be difficult to track down and can lead to denial of service with API users. We need a mechanism to ensure MarkPools instances are never leaked, and to also discover bugs that would cause them to leak.

      See the folloiwng thread for a more detailed discussion of the problems: https://lists.apache.org/thread.html/914d5e7e0e4bf9001cb048aaaa034608b1b6bcffa04de9a10158302e@%3Cdev.daffodil.apache.org%3E

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                slawrence Steve Lawrence
                Reporter:
                slawrence Steve Lawrence
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m