You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Alan M. Carroll (JIRA)" <ji...@apache.org> on 2014/03/02 04:25:19 UTC

[jira] [Commented] (TS-2019) find out what is the problem of reporting OpenReadHead failed on vector inconsistency

    [ https://issues.apache.org/jira/browse/TS-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917277#comment-13917277 ] 

Alan M. Carroll commented on TS-2019:
-------------------------------------

fbana provided a machine that was able to reproduce this problem. As a result I tracked this down to the UrlPrintHack logic in HTTP.cc. What happens is m_ptr_host can be set to point in to the MIME data if the host isn't in the URL. When this is marshalled, m_ptr_host is checked against the URL heap and the marshal fails because it is not in there (it's in the MIME heap). As a result of that, the marshal for the request header returns -1 instead of a length. This isn't checked so instead of a fail the buffer pointer is backed up one byte and the is response header written over the request header. As a result when this unmarshalling is attempted on this mess it doesn't work and you get the error message. I am pondering how to deal with this, as there are good reasons for moving the m_ptr_host value, but perhaps we've done enough work to change the host request to go through the header object and not the URL that we can drop that.

> find out what is the problem of reporting OpenReadHead failed on vector inconsistency
> -------------------------------------------------------------------------------------
>
>                 Key: TS-2019
>                 URL: https://issues.apache.org/jira/browse/TS-2019
>             Project: Traffic Server
>          Issue Type: Task
>          Components: Cache
>            Reporter: Zhao Yongming
>            Assignee: Alan M. Carroll
>            Priority: Critical
>             Fix For: 5.0.0
>
>
> {code}
> [Jul 10 19:40:33.170] Server {0x2aaaaaaf1680} NOTE: OpenReadHead failed for cachekey 44B5C68B : vector inconsistency with 4624
> [Jul 10 19:40:33.293] Server {0x2aaaaaaf1680} NOTE: OpenReadHead failed for cachekey 2ABA746F : vector inconsistency with 4632
> [Jul 10 19:40:33.368] Server {0x2aaaaaaf1680} NOTE: OpenReadHead failed for cachekey 389594A0 : vector inconsistency with 4632
> [Jul 10 19:40:33.399] Server {0x2aaaaaaf1680} NOTE: OpenReadHead failed for cachekey FBC601A3 : vector inconsistency with 4632
> [Jul 10 19:40:33.506] Server {0x2aaaaaaf1680} NOTE: OpenReadHead failed for cachekey 1F39AD5F : vector inconsistency with 4632
> [Jul 10 19:40:33.602] Server {0x2aaaaaaf1680} NOTE: OpenReadHead failed for cachekey ABFC6D97 : vector inconsistency with 4632
> [Jul 10 19:40:33.687] Server {0x2aaaaaaf1680} NOTE: OpenReadHead failed for cachekey 2420ABBF : vector inconsistency with 4632
> [Jul 10 19:40:33.753] Server {0x2aaaaaaf1680} NOTE: OpenReadHead failed for cachekey 5DD061C8 : vector inconsistency with 4632
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)