[ https://issues.apache.org/jira/browse/TS-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649264#comment-14649264 ]
ASF subversion and git services commented on TS-1007: ----------------------------------------------------- Commit 2805dd266ac2ab17b97365fd69d3208b03a68a96 in trafficserver's branch refs/heads/6.0.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=2805dd2 ] Merge branch 'master' into 6.0.x * master: Revert "TS-1007: SSLN Close called before TXN Close. This closes #249." TS-3806 Resolve undefined reference to symbol MD5_Final > 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)