[ 
https://issues.apache.org/jira/browse/TS-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331707#comment-15331707
 ] 

ASF GitHub Bot commented on TS-4507:
------------------------------------

GitHub user shinrich opened a pull request:

    https://github.com/apache/trafficserver/pull/717

    TS-4507: Fixes to ensure SSN_CLOSE called after TXN_CLOSE.

    Adding logic to ensure that SSN_CLOSE doesn't get called before TXN_CLOSE. 
This involved deferring the session destroy further.  Had to add some recursion 
checks in HTTP2 to make sure we don't destroy the ssn object on the stack.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shinrich/trafficserver ts-4507

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/717.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #717
    
----
commit 2cd181fc0294de17ca0386a33ae45be06780d496
Author: shinrich <[email protected]>
Date:   2016-06-15T12:48:49Z

    TS-4507: Fixes to ensure SSN_CLOSE called after TXN_CLOSE.

----


> 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)

Reply via email to