trafficserver-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leif Hedstrom (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TS-245) Traffic server crashed when configured with min os keep alive connection and debug logging
Date Sat, 17 Apr 2010 04:09:29 GMT

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

Leif Hedstrom updated TS-245:
-----------------------------

    Fix Version/s: 2.1.0

> Traffic server crashed when configured with min os keep alive connection and debug logging
> ------------------------------------------------------------------------------------------
>
>                 Key: TS-245
>                 URL: https://issues.apache.org/jira/browse/TS-245
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0a
>         Environment: OS: rhel 4.7
>            Reporter: Qinghong Zhang
>            Assignee: Bryan Call
>             Fix For: 2.1.0
>
>         Attachments: debug_bcall_001.diff
>
>
> The crash seems to happen when logging the information: [session_bucket] session received
io notice [VC_EVENT_ACTIVE_TIMEOUT].
> The core stack is:
> #0  0x006f9b6b in strlen () from /lib/tls/libc.so.6
> #1  0x006cd756 in vfprintf () from /lib/tls/libc.so.6
> #2  0x006ca0bc in buffered_vfprintf () from /lib/tls/libc.so.6
> #3  0x006ca2fb in vfprintf () from /lib/tls/libc.so.6
> #4  0x082ef1d1 in Diags::print_va (this=0x8468e30, debug_tag=0x831f814 "http_ss", diags_level=DL_Debug,
prefix=0x0, loc=0x0, 
>     format_string=0x831fa1c "[%b64d] [session_bucket] session received io notice [%s],
reseting timeout to maintain minimum number of connections", 
>     ap=0x5a5a16c "\001", wID=0, eIST=keNo_OP) at Diags.cc:321
> #5  0x082ef880 in DiagsDClosure::operator() (this=0x5a5a200, tag=0x831f814 "http_ss",

>     format_string=0x831fa1c "[%b64d] [session_bucket] session received io notice [%s],
reseting timeout to maintain minimum number of connections")
>     at Diags.h:255
> #6  0x0815311d in SessionBucket::session_handler (this=0x83ef7f4, event=106, data=0x929bb2c)
at ../../libinktomi++/Diags.h:341
> #7  0x082cab3f in UnixNetVConnection::mainEvent (this=0x929baa0, event=2, e=0x926e670)
at ../../iocore/eventsystem/I_Continuation.h:146
> #8  0x082ec8b0 in EThread::process_event (this=0xb799d008, e=0x926e670, calling_code=2)
at I_Continuation.h:146
> #9  0x082ecf6e in EThread::execute (this=0xb799d008) at UnixEThread.cc:202
> #10 0x082ead6c in spawn_thread_internal (a=0x85338f8) at Thread.cc:85
> #11 0x008463cc in start_thread () from /lib/tls/libpthread.so.0
> #12 0x0075b96e in clone () from /lib/tls/libc.so.6
> If the -T option is turned off, no crash is observed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message