[
https://issues.apache.org/jira/browse/DAFFODIL-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-1862.
-----------------------------------
pulled latest updates for incubator-daffodil which included the specified
commit, 541bb07801d44e976d2feb256cc04735268445b0.
Reviewed the code and talked with dev and determined that it would be very
difficult to simulate a condition that would trigger a markpool leak.
Determined that the code reviews would be sufficient in this case.
Verified that the system successfully built and executed the sbt tests. Nightly
run also executed successfully.
> Better logging/reset mechanism for MarkPool
> -------------------------------------------
>
> Key: DAFFODIL-1862
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1862
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Reporter: Steve Lawrence
> Assignee: Steve Lawrence
> Fix For: 2.1.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
