Uploaded image for project: 'Traffic Server'
  1. Traffic Server
  2. TS-1007

SSN Close called before TXN Close

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.1
    • Fix Version/s: 6.2.0
    • Component/s: TS API
    • Labels:

      Description

      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!

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                shinrich Susan Hinrichs
                Reporter:
                nick@webthing.com Nick Kew
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: