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 2015/07/24 02:36:04 UTC

[jira] [Updated] (TS-3795) Invalid assertion in handle_server_connection_not_open

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

Alan M. Carroll updated TS-3795:
--------------------------------
    Summary: Invalid assertion in handle_server_connection_not_open  (was: Invalid assertion in handle_server_connection_not_op)

> Invalid assertion in handle_server_connection_not_open
> ------------------------------------------------------
>
>                 Key: TS-3795
>                 URL: https://issues.apache.org/jira/browse/TS-3795
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 6.1.0
>            Reporter: Alan M. Carroll
>            Priority: Minor
>             Fix For: sometime
>
>
> In {{HttpTransact::handle_server_connection_not_open}} there is an early assert
> {code}
> ink_assert(s->current.server->had_connect_fail());
> {code}
> However, in {{HttpTransact::handle_response_from_server}} the cases of a parse error, connection closed, or a bad response all call this method and in none of these cases was there a connection failure. This causes an assertion which, to me, seems unreasonable.



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