[jira] [Commented] (TS-3189) Do not start reading data on server to user agent tunnel too soon

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

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

Sudheer Vinukonda commented on TS-3189:
---------------------------------------

Hi [~shinrich] - I was testing 5.2 on a prod host and it looks like the commit in TS-3189 may result in a core dump (pls see TS-3248). 

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

I've reverted TS-3248 and don't see a core so far, but, will monitor further and update.

> Do not start reading data on server to user agent tunnel too soon
> -----------------------------------------------------------------
>
>                 Key: TS-3189
>                 URL: https://issues.apache.org/jira/browse/TS-3189
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Susan Hinrichs
>            Assignee: Susan Hinrichs
>             Fix For: 5.2.0
>
>
> The original logic would set up a do_io_read for max_int in HttpSM::attach_server_session.
> However, at this point there still may be things finishing up in the user_agent to server tunnel (for posts).  We were seeing occasional cases of the EOS for the tunnel to user_agent communication being incorrectly delivered to the consumer of the user_agent to server tunnel.
> It is sufficient to set up a 0 length read in HttpSM::attach_server_session.  This will enable the correct handlers to deal with inactivity timeouts.  Then we can setup the real read in HttpSM::setup_server_read_response_header() after we know that the user_agent to origin server tunnel has been taken down. 



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