[
https://issues.apache.org/jira/browse/TS-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649261#comment-14649261
]
ASF subversion and git services commented on TS-1007:
-----------------------------------------------------
Commit 1d1eaa6988f31a46e5fea89ea49294f9486bfb14 in trafficserver's branch
refs/heads/6.0.x from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1d1eaa6 ]
Revert "TS-1007: SSLN Close called before TXN Close. This closes #249."
This reverts commit 2e0689748b496e54977fa99d2f7f4c75915da1df.
This breaks in multiple ways, see TS-3804 and TS-3805. Sudheer was able to fix
one, but we stopped after a few unsuccessful attempts on the second. We should
move out TS-1007, TS-3804 and TS-3805 until later.
> SSN Close called before TXN Close
> ---------------------------------
>
> Key: TS-1007
> URL: https://issues.apache.org/jira/browse/TS-1007
> Project: Traffic Server
> Issue Type: Bug
> Components: TS API
> Affects Versions: 3.0.1
> Reporter: Nick Kew
> Assignee: Susan Hinrichs
> Labels: incompatible
> Fix For: 6.1.0
>
>
> Where a plugin implements both SSN_CLOSE_HOOK and TXN_CLOSE_HOOK, the
> SSN_CLOSE_HOOK is called first of the two. This messes up normal cleanups!
> Details:
> Register a SSN_START event globally
> In the SSN START, add a TXN_START and a SSN_CLOSE
> In the TXN START, add a TXN_CLOSE
> Stepping through, I see the order of events actually called, for the simple
> case of a one-off HTTP request with no keepalive:
> SSN_START
> TXN_START
> SSN_END
> TXN_END
> Whoops, SSN_END cleaned up the SSN context, leaving dangling pointers in the
> TXN!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
