[jira] [Updated] (TS-3985) TSHttpTxnCacheLookupStatusSet(HIT_STALE) calls cause a crash

["song (JIRA)" <ji...@apache.org>]

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

song updated TS-3985:
---------------------
    Affects Version/s: 6.0.0
          Environment: Cache Single Fragment
          Description: 
Dear all

In CacheVC::openReadStartHead function, it is unnecessary to calculate the next key with a single fragment, because we have already done for a read operation.Why do we do this. 

  was:
Dear

ATS cause a crash in how_to_open_connection  while using TSHttpTxnCacheLookupStatusSet . In Function HttpTransact::HandleCacheOpenReadHit, the hook pending_work was set to issue_revalidate function and the variable " s->current.request_to = ORIGIN_SERVER". But the hook  only be released while talking to a parent proxy in PPDNSLookup function. How to fix it.

thanks

          Component/s:     (was: DNS)
           Issue Type: Improvement  (was: Bug)

> TSHttpTxnCacheLookupStatusSet(HIT_STALE) calls cause a crash
> ------------------------------------------------------------
>
>                 Key: TS-3985
>                 URL: https://issues.apache.org/jira/browse/TS-3985
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Cache
>    Affects Versions: 6.0.0
>         Environment: Cache Single Fragment
>            Reporter: song
>              Labels: Review
>             Fix For: 6.1.0
>
>         Attachments: untitled.diff
>
>
> Dear all
> In CacheVC::openReadStartHead function, it is unnecessary to calculate the next key with a single fragment, because we have already done for a read operation.Why do we do this. 



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