[
https://issues.apache.org/jira/browse/TS-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933566#comment-14933566
]
James Peach commented on TS-3950:
---------------------------------
We might be able to help this effort by adding some extra support to the event
processing layer. If we can poison continuations in such a way that the event
system can tell whether it is delivering an event to a dead object, we have a
better shot at tracking this down and at verifying when the handling is
correct. We should also consider whether we can detect re-used objects (using
an explicit generation count, or maybe the free list version?).
> PluginVC receives events after it's already closed.
> ---------------------------------------------------
>
> Key: TS-3950
> URL: https://issues.apache.org/jira/browse/TS-3950
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, Plugins
> Reporter: Sudheer Vinukonda
>
> This is a follow up to TS-3949. It looks like PluginVC receives events (read,
> write, timeout etc) even after it's already closed. It currently ignores
> those events by checking the *closed* state. However, this looks to be
> inherently incorrect, since, accessing the data inside an already closed
> pluginVC is fraught with bugs (e.g. it could have been reallocated etc).
> Opening this jira to track the problem and see if it can be fixed better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
