[
https://issues.apache.org/jira/browse/TS-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344617#comment-15344617
]
ASF GitHub Bot commented on TS-4507:
------------------------------------
Github user jpeach commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/717#discussion_r68082470
--- Diff: proxy/http/Http1ClientSession.cc ---
@@ -82,11 +82,21 @@ Http1ClientSession::Http1ClientSession()
void
Http1ClientSession::destroy()
{
+}
+
+void
+Http1ClientSession::really_destroy()
--- End diff --
Really? Can you please elaborate on why another layer of destroy is needed?
It seems fairly ugly to me :-/
> It is still possible for SSN_CLOSE hook to be called before TXN_CLOSE hook
> --------------------------------------------------------------------------
>
> Key: TS-4507
> URL: https://issues.apache.org/jira/browse/TS-4507
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Susan Hinrichs
> Assignee: Susan Hinrichs
> Fix For: 7.0.0
>
>
> One of our plugins will occasionally crash. It appears there is still a path
> for HTTP2 that has the SSN_CLOSE hook close before the TXN_CLOSE hook.
> Working through solutions that delay the SSN_CLOSE hook until after all the
> TXN_CLOSE hooks, but does not lose the SSN_CLOSE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
