[
https://issues.apache.org/jira/browse/TS-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan M. Carroll updated TS-4495:
--------------------------------
Description: The {{RemapPlugin}} class calls {{getTransaction}} which
lazily creates a transaction object. But In this case no other hooks are set
which results in the {{Transaction}} instance being leaked. This is not
observed (as far as we know) in deployment because the presence of any
{{GlobalPlugin}} will set the hook and clean up the shared {{Transaction}}
instance. Nevertheless the pure remap case should not leak. (was: The
{{RemapPlugin}} class calls {{getTransaction}} which lazily creates a
transaction object. But In this case no other hooks are sets which results in
the {{Transaction}} instance being leaked. This is not observed (as far as we
know) in deployment because the presence of any {{GlobalPlugin}} will set the
hook and clean up the shared {{Transaction}} instance. Nevertheless the pure
remap case should not leak.)
> RemapPlugin can leak Transaction instances
> ------------------------------------------
>
> Key: TS-4495
> URL: https://issues.apache.org/jira/browse/TS-4495
> Project: Traffic Server
> Issue Type: Bug
> Components: CPP API
> Reporter: Alan M. Carroll
> Assignee: Brian Geffon
> Fix For: 7.0.0
>
>
> The {{RemapPlugin}} class calls {{getTransaction}} which lazily creates a
> transaction object. But In this case no other hooks are set which results in
> the {{Transaction}} instance being leaked. This is not observed (as far as we
> know) in deployment because the presence of any {{GlobalPlugin}} will set the
> hook and clean up the shared {{Transaction}} instance. Nevertheless the pure
> remap case should not leak.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
