You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2003/01/13 20:27:17 UTC

DO NOT REPLY [Bug 16039] New: - Log4J shutdown not invoked?

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=16039>.
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=16039

Log4J shutdown not invoked?

           Summary: Log4J shutdown not invoked?
           Product: Commons
           Version: Nightly Builds
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Logging
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: william.pohlmann@vertexinc.com


There's a comment in Log4jFactory.release() that suggests that log4j isn't 
being cleaned up.  (// what's the log4j mechanism to cleanup ???)

I think the appropriate method to call would be LogManager.shutdown().

A cursory look through log4j suggests that failure to shutdown may result in 
the SocketAppender not completely flushing data.  This is an UNCONFIRMED 
observation from reading code.  This would be a more serious problem than just 
failing garbage collection in some environments.

At least this is probably the call you want there, if it isn't truly a critical 
bug.

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