[
https://issues.apache.org/jira/browse/TS-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766573#comment-13766573
]
Alan M. Carroll commented on TS-2211:
-------------------------------------
My interpretation - the NetVC socket level logic reads the data from the origin
socket. It then signals down the VC chain that data is ready. This arrives at
the HttpTunnel logic which passes it on from producer (origin socket) to
consumer (client VC). The client VC then calls reenable on the VIO but, because
the VIO is marked as enabled, nothing is done. As noted, this indicates the VIO
was unscheduled / disabled while be left in a marked state. I think it likely
that it was unmarked correctly and then, in the SSL logic, marked as enabled
without really being enabled. The SSL logic does a lot of mucking about with
scheduling VCs and playing with the enable marks. Given this does not happen in
the non-SSL case, that seems a strong case.
The key trigger is that data is read from the origin socket, and then written
to the client socket before more data from the origin arrives, that is the SSL
logic executes the case that it wants to write to the client socket but no data
is available.
> SSL client connections hang and a aborted due to inactivity
> -----------------------------------------------------------
>
> Key: TS-2211
> URL: https://issues.apache.org/jira/browse/TS-2211
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP, SSL
> Reporter: Theo Schlossnagle
> Fix For: 4.1.0
>
>
> Test setup:
> ATS in reverse proxy mode. Terminating SSL for clients, remap to non-SSL for
> origin. Origin delays 10s before sending any data (including headers), then
> dumps a non-chunked response (Content-Length) of about 3Mbytes.
> Over slow client connections, the client session freezes mid download (around
> 256k in my tests)... hangs until the inactivity timer fires and snips all the
> connections.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
