You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Thomas Jackson (JIRA)" <ji...@apache.org> on 2013/07/20 00:58:48 UTC
[jira] [Commented] (TS-2052) ET_SSL thread spinning
[ https://issues.apache.org/jira/browse/TS-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714191#comment-13714191 ]
Thomas Jackson commented on TS-2052:
------------------------------------
I've taken a core dump but i'm not sure how to convert pids <-> gdb threads. I only see 2 threads doing anything interesting:
64 Thread 0x2aae95edb700 (LWP 6602) 0x000000000056d367 in HttpSM::state_read_client_request_header (this=0x2aaec0095cf0, event=102, data=0x2aaed0033a98) at HttpSM.cc:720
52 Thread 0x2aae952cf700 (LWP 6590) 0x000000000055bbbb in HttpSM::add_history_entry (this=0x2ab0d015c7b0, fileline=0x700006 "HttpSM.cc:667", event=102, reentrant=1) at HttpSM.h:578
bt of thread 52:
#0 0x000000000055bbbb in HttpSM::add_history_entry (this=0x2ab0d015c7b0, fileline=0x700006 "HttpSM.cc:667", event=102, reentrant=1) at HttpSM.h:578
#1 0x000000000056d0e2 in HttpSM::state_read_client_request_header (this=0x2ab0d015c7b0, event=102, data=0x2aaed00ba888) at HttpSM.cc:667
#2 0x00000000005728af in HttpSM::main_handler (this=0x2ab0d015c7b0, event=102, data=0x2aaed00ba888) at HttpSM.cc:2444
#3 0x00000000004ec922 in Continuation::handleEvent (this=0x2ab0d015c7b0, event=102, data=0x2aaed00ba888) at ../iocore/eventsystem/I_Continuation.h:146
#4 0x00000000006bafe8 in read_signal_and_update (event=102, vc=0x2aaed00ba780) at UnixNetVConnection.cc:138
#5 0x00000000006bb139 in read_signal_done (event=102, nh=0x2aae939ba208, vc=0x2aaed00ba780) at UnixNetVConnection.cc:168
#6 0x00000000006bd57e in UnixNetVConnection::readSignalDone (this=0x2aaed00ba780, event=102, nh=0x2aae939ba208) at UnixNetVConnection.cc:884
#7 0x00000000006afb64 in SSLNetVConnection::net_read_io (this=0x2aaed00ba780, nh=0x2aae939ba208, lthread=0x2aae939b7010) at SSLNetVConnection.cc:242
#8 0x00000000006b7e26 in NetHandler::mainNetEvent (this=0x2aae939ba208, event=5, e=0x26a1fc0) at UnixNet.cc:380
#9 0x00000000004ec922 in Continuation::handleEvent (this=0x2aae939ba208, event=5, data=0x26a1fc0) at ../iocore/eventsystem/I_Continuation.h:146
#10 0x00000000006dc29e in EThread::process_event (this=0x2aae939b7010, e=0x26a1fc0, calling_code=5) at UnixEThread.cc:142
#11 0x00000000006dc793 in EThread::execute (this=0x2aae939b7010) at UnixEThread.cc:264
#12 0x00000000006db58b in spawn_thread_internal (a=0x2a00410) at Thread.cc:88
#13 0x000000323a207851 in start_thread () from /lib64/libpthread.so.0
#14 0x0000003239ee890d in clone () from /lib64/libc.so.6
bt of thread 64
#0 0x000000000056d367 in HttpSM::state_read_client_request_header (this=0x2aaec0095cf0, event=102, data=0x2aaed0033a98) at HttpSM.cc:720
#1 0x00000000005728af in HttpSM::main_handler (this=0x2aaec0095cf0, event=102, data=0x2aaed0033a98) at HttpSM.cc:2444
#2 0x00000000004ec922 in Continuation::handleEvent (this=0x2aaec0095cf0, event=102, data=0x2aaed0033a98) at ../iocore/eventsystem/I_Continuation.h:146
#3 0x00000000006bafe8 in read_signal_and_update (event=102, vc=0x2aaed0033990) at UnixNetVConnection.cc:138
#4 0x00000000006bb139 in read_signal_done (event=102, nh=0x2aae945c6208, vc=0x2aaed0033990) at UnixNetVConnection.cc:168
#5 0x00000000006bd57e in UnixNetVConnection::readSignalDone (this=0x2aaed0033990, event=102, nh=0x2aae945c6208) at UnixNetVConnection.cc:884
#6 0x00000000006afb64 in SSLNetVConnection::net_read_io (this=0x2aaed0033990, nh=0x2aae945c6208, lthread=0x2aae945c3010) at SSLNetVConnection.cc:242
#7 0x00000000006b7e26 in NetHandler::mainNetEvent (this=0x2aae945c6208, event=5, e=0x26a16c0) at UnixNet.cc:380
#8 0x00000000004ec922 in Continuation::handleEvent (this=0x2aae945c6208, event=5, data=0x26a16c0) at ../iocore/eventsystem/I_Continuation.h:146
#9 0x00000000006dc29e in EThread::process_event (this=0x2aae945c3010, e=0x26a16c0, calling_code=5) at UnixEThread.cc:142
#10 0x00000000006dc793 in EThread::execute (this=0x2aae945c3010) at UnixEThread.cc:264
#11 0x00000000006db58b in spawn_thread_internal (a=0x2ac46a0) at Thread.cc:88
#12 0x000000323a207851 in start_thread () from /lib64/libpthread.so.0
#13 0x0000003239ee890d in clone () from /lib64/libc.so.6
> ET_SSL thread spinning
> ----------------------
>
> Key: TS-2052
> URL: https://issues.apache.org/jira/browse/TS-2052
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Thomas Jackson
>
> I'm running ATS 3.2.4 and as I was benchmarking ATS for SSL usage I noticed that the CPU usage would go up dramatically even after I had stopped the test. After running a benchmark I am able to get an ET_SSL thread stuck spinning (100% cpu in top).
> I am also able to reproduce this off master from git.
> To reproduce:
> - setup trafficserver with ssl port
> - siege -b -c 1000 -n 100 https://hostname/path
> let it sit for 1-5minutes and one of the ET_SSL threads will be stuck spinning.
--
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