DO NOT REPLY [Bug 16468] New: - Thread overrun causes message buffer to clear without being flushed

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16468>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16468

Thread overrun causes message buffer to clear without being flushed

           Summary: Thread overrun causes message buffer to clear without
                    being flushed
           Product: Log4j
           Version: 1.2
          Platform: All
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Appender
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: brennan.w.stehling@jci.com


Inside several servlets a Logger is used to log messages for critical
exceptions.  It appears that when this happens the thread ends immediately but
no messages are written to the log.  I believe this is due to a thread overrun.
 The message buffer is being destroyed by the dying thread before it can write
the messages.

By placing the appender/writer onto an independent thread it may be possible to
allow the buffer to remain safe when the servlet thread dies.  I would be happy
to help resolve problem, but I will need some help with getting started and some
guidance along the way.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>