You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Sudheer Vinukonda (JIRA)" <ji...@apache.org> on 2014/04/23 22:40:20 UTC
[jira] [Updated] (TS-2740) Enhancements and Fixes to SPDY support
in ATS
[ https://issues.apache.org/jira/browse/TS-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sudheer Vinukonda updated TS-2740:
----------------------------------
Description:
Would like to use this Jira to make fixes/enhancements identified during our tests to adapt SPDY in our production environment
1. Currently, SPDY can only be turned on/off via the build with --enable-spdy option. Would like to add a configuration control to turn on/off SPDY capability (useful to troubleshoot production issues) when built with --enable-spdy option.
2. Noticed ATS crashing with the below stack trace during production. Looks like TsFetchCreate() asserts for non-ipv4 address.
[TrafficServer] using root directory '/home/y'
FATAL: InkAPI.cc:7295: failed assert `ats_is_ip4(client_addr)`
/home/y/bin/traffic_server - STACK TRACE:
/home/y/lib64/libtsutil.so.5(+0x1f5c8)[0x2b8d706445c8]
/home/y/lib64/libtsutil.so.5(+0x1da8f)[0x2b8d70642a8f]
/home/y/bin/traffic_server(TSFetchCreate+0x57)[0x4b0fb7]
/home/y/bin/traffic_server[0x5d24df]
/home/y/bin/traffic_server(_Z26spdy_on_ctrl_recv_callbackP15spdylay_session18spdylay_frame_typeP13spdylay_framePv+0x6fe)[0x5d32fe]
/home/y/bin/traffic_server(spdylay_session_on_syn_stream_received+0xe0)[0x718b30]
/home/y/bin/traffic_server(spdylay_session_mem_recv+0xb47)[0x719837]
/home/y/bin/traffic_server(spdylay_session_recv+0x49)[0x719a69]
/home/y/bin/traffic_server[0x5d09c8]
/home/y/bin/traffic_server(_ZN18UnixNetVConnection19readSignalAndUpdateEi+0x27)[0x6ed907]
/home/y/bin/traffic_server(_ZN17SSLNetVConnection11net_read_ioEP10NetHandlerP7EThread+0xf37)[0x6ddb07]
/home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1f2)[0x6e4f72]
/home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x712f0f]
/home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x7138b3]
FATAL: InkAPI.cc:7295: failed assert `ats_is_ip4(client_addr)`
/home/y/bin/traffic_server[0x7122ba]
/lib64/libpthread.so.0(+0x3297207851)[0x2b8d70cdb851]
/lib64/libc.so.6(clone+0x6d)[0x3296ee890d]
was:
Currently, SPDY can only be turned on/off via the build with --enable-spdy option. Would like to add a configuration control to turn on/off SPDY capability (useful to troubleshoot production issues) when built with --enable-spdy option.
Would like to use this Jira to also add support of any other SPDY related settings that might be useful.
Summary: Enhancements and Fixes to SPDY support in ATS (was: Configuration settings to SPDY support in ATS)
Thanks for the inputs, James - I've modified the ticket to track all the issues identified during our SPDY adaption.
> Enhancements and Fixes to SPDY support in ATS
> ---------------------------------------------
>
> Key: TS-2740
> URL: https://issues.apache.org/jira/browse/TS-2740
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core
> Reporter: Sudheer Vinukonda
>
> Would like to use this Jira to make fixes/enhancements identified during our tests to adapt SPDY in our production environment
> 1. Currently, SPDY can only be turned on/off via the build with --enable-spdy option. Would like to add a configuration control to turn on/off SPDY capability (useful to troubleshoot production issues) when built with --enable-spdy option.
> 2. Noticed ATS crashing with the below stack trace during production. Looks like TsFetchCreate() asserts for non-ipv4 address.
> [TrafficServer] using root directory '/home/y'
> FATAL: InkAPI.cc:7295: failed assert `ats_is_ip4(client_addr)`
> /home/y/bin/traffic_server - STACK TRACE:
> /home/y/lib64/libtsutil.so.5(+0x1f5c8)[0x2b8d706445c8]
> /home/y/lib64/libtsutil.so.5(+0x1da8f)[0x2b8d70642a8f]
> /home/y/bin/traffic_server(TSFetchCreate+0x57)[0x4b0fb7]
> /home/y/bin/traffic_server[0x5d24df]
> /home/y/bin/traffic_server(_Z26spdy_on_ctrl_recv_callbackP15spdylay_session18spdylay_frame_typeP13spdylay_framePv+0x6fe)[0x5d32fe]
> /home/y/bin/traffic_server(spdylay_session_on_syn_stream_received+0xe0)[0x718b30]
> /home/y/bin/traffic_server(spdylay_session_mem_recv+0xb47)[0x719837]
> /home/y/bin/traffic_server(spdylay_session_recv+0x49)[0x719a69]
> /home/y/bin/traffic_server[0x5d09c8]
> /home/y/bin/traffic_server(_ZN18UnixNetVConnection19readSignalAndUpdateEi+0x27)[0x6ed907]
> /home/y/bin/traffic_server(_ZN17SSLNetVConnection11net_read_ioEP10NetHandlerP7EThread+0xf37)[0x6ddb07]
> /home/y/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x1f2)[0x6e4f72]
> /home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x712f0f]
> /home/y/bin/traffic_server(_ZN7EThread7executeEv+0x493)[0x7138b3]
> FATAL: InkAPI.cc:7295: failed assert `ats_is_ip4(client_addr)`
> /home/y/bin/traffic_server[0x7122ba]
> /lib64/libpthread.so.0(+0x3297207851)[0x2b8d70cdb851]
> /lib64/libc.so.6(clone+0x6d)[0x3296ee890d]
--
This message was sent by Atlassian JIRA
(v6.2#6252)