logging-log4cxx-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "hydrargentum@gmail.com" <hydrargen...@gmail.com>
Subject RollingFileAppender crashes under heavy async load
Date Tue, 27 May 2008 11:52:00 GMT
#0  0x009bb402 in __kernel_vsyscall ()
#1  0x0042cba0 in raise () from /lib/libc.so.6
#2  0x0042e4b1 in abort () from /lib/libc.so.6
#3  0x003a8540 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#4  0x003a6025 in std::set_unexpected () from /usr/lib/libstdc++.so.6
#5  0x003a6062 in std::terminate () from /usr/lib/libstdc++.so.6
#6  0x003a619a in __cxa_throw () from /usr/lib/libstdc++.so.6
#7  0x001fb161 in log4cxx::helpers::FileOutputStream::write (this=0x885ff48,
    buf=@0xb2755a58) at fileoutputstream.cpp:91
#8  0x00252e46 in log4cxx::rolling::CountingOutputStream::write
    buf=@0xb2755a58, p=@0xb2755c3c) at rollingfileappender.cpp:346
#9  0x0023a4de in log4cxx::helpers::OutputStreamWriter::write
    str=@0xb2755aa8, p=@0xb2755c3c) at outputstreamwriter.cpp:69
#10 0x0027d8e1 in log4cxx::WriterAppender::subAppend (this=0x8122df8,
    event=@0xb2755c34, p=@0xb2755c3c) at writerappender.cpp:212
#11 0x002528d7 in log4cxx::rolling::RollingFileAppenderSkeleton::subAppend (
    this=0x8122df8, event=@0xb2755c34, p=@0xb2755c3c)
    at rollingfileappender.cpp:256
#12 0x0027d4cc in log4cxx::WriterAppender::append (this=0x8122df8,
    event=@0xb2755c34, pool1=@0xb2755c3c) at writerappender.cpp:88
#13 0x001c714d in log4cxx::AppenderSkeleton::doAppend (this=0x8122df8,
    event=@0xb2755c34, pool1=@0xb2755c3c) at appenderskeleton.cpp:142
#14 0x001c4262 in
    (this=0x8122ea0, event=@0xb2755c34, p=@0xb2755c3c)
    at appenderattachableimpl.cpp:69
#15 0x0021c3c6 in log4cxx::Logger::callAppenders (this=0x80ed028,
    event=@0xb2755c34, p=@0xb2755c3c) at logger.cpp:93
#16 0x0021d9bb in log4cxx::Logger::forcedLog (this=0x80ed028,
    message=@0xb2755cd0, location=@0xb2755cdc) at logger.cpp:124
#17 0x08071939 in network::HTTPWorker::_debugCallback (handle=0xb2f507d0,
    data=0xb2755e6b "About to serve() (#0)\n",
    size=23, obj=0x0) at src/network/HTTPWorker.cpp:274

Runing under CentOS 5.1

It repeated for 2 times at the same class (in various callback), callback of
this class is called async when workers finished it's job.

As as think it somewhat linked with condition when RollingFileAppender in is
just rolledout logfile, since i have just one record in newfile (this also
repeat for 2 times).
Maybe unsynchronized code there, so one thread roll file out and close file
handle when other writes in ?

View raw message