You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2014/12/16 19:47:15 UTC

[jira] [Resolved] (TS-3096) After TS-2751 TSVConnClosedGet changed its behaviour

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

Leif Hedstrom resolved TS-3096.
-------------------------------
    Resolution: Duplicate

Oh, this is a dupe of TS-3058. It just wasn't marked properly.

> After TS-2751 TSVConnClosedGet changed its behaviour
> ----------------------------------------------------
>
>                 Key: TS-3096
>                 URL: https://issues.apache.org/jira/browse/TS-3096
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: TS API
>            Reporter: Daniel Vitor Morilha
>            Priority: Critical
>
> One of our plug-ins initiates a background connection to an origin by using TSHttpConnect API.
> While handling the continuation events (WRITE, READ) the plug-in checks if the vconnection is still open by calling TSVConnClosedGet(vconnection).
> ATS recently changed the behavior. Now TSVConnClosedGet(vconnections) returns a value different than 0 before any data can be retrieved.
> If the call to TSVConnClosedGet is ignored the plug-in successfully writes the request and receives the response.
> By investigation our different Traffic Server versions the described change seems to be related with TS-2751. 



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