You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/08/02 14:29:20 UTC
[jira] [Work logged] (TS-4507) It is still possible for SSN_CLOSE
hook to be called before TXN_CLOSE hook
[ https://issues.apache.org/jira/browse/TS-4507?focusedWorklogId=26145&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26145 ]
ASF GitHub Bot logged work on TS-4507:
--------------------------------------
Author: ASF GitHub Bot
Created on: 02/Aug/16 14:28
Start Date: 02/Aug/16 14:28
Worklog Time Spent: 10m
Work Description: Github user SolidWallOfCode commented on the issue:
https://github.com/apache/trafficserver/pull/787
I've reviewed the changes and I don't think they can really be split up. Part of the reason is similar changes in both the HTTP/1 and HTTP/2 classes, which makes the change appear bigger than it is. I'm +1 on committing this, especially since we've been successfully testing them in production inside Yahoo!.
Issue Time Tracking
-------------------
Worklog Id: (was: 26145)
Time Spent: 50m (was: 40m)
> 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
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> 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)