You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Susan Hinrichs (JIRA)" <ji...@apache.org> on 2016/09/26 23:43:20 UTC

[jira] [Updated] (TS-4896) TSHttpTxnClientAddrGet and TSHttpTxnIncomingAddrGet may return NULL

     [ https://issues.apache.org/jira/browse/TS-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Susan Hinrichs updated TS-4896:
-------------------------------
    Priority: Minor  (was: Major)

> TSHttpTxnClientAddrGet and TSHttpTxnIncomingAddrGet may return NULL
> -------------------------------------------------------------------
>
>                 Key: TS-4896
>                 URL: https://issues.apache.org/jira/browse/TS-4896
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>            Reporter: Susan Hinrichs
>            Priority: Minor
>
> With the clean up rearranging to ensure SSN close occurs after TXN close (TS-4507), the API calls TSHttpTxnClientAddrGet and TSHttpTxnIncomingAddrGet may return NULL.  This can occur in the case where the client connection has terminated, but the HttpSM has not yet shutdown.  We now null out the reference in HttpSM to the client_vc.  These calls fetch the addresses from the client_vc, so it HttpSM reference to it has been removed, these API's will return NULL.
> Locally, we copy these addresses into the ProxyClientSession before the client_vc is disconnected.  We had push back from deployed plugins for a short term fix.  
> Not clear what if anything we want to do in open source.  But wanted people to be aware that this is an issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)