You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2003/01/21 01:16:10 UTC

DO NOT REPLY [Bug 16280] New: - Error Message always logged to log4j when calling close() on TelnetAppender

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

Error Message always logged to log4j when calling close() on TelnetAppender

           Summary: Error Message always logged to log4j when calling
                    close() on TelnetAppender
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Appender
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: elmattador@hotmail.com


When close() is called on TelnetAppender a java.net.SocketException will always
be thrown in the run() method of inner class SocketHandler.  This forces the
error log: "LogLog.error("Encountered error while in SocketHandler loop.", e);"
on line 166 to be executed, thus logging information that frightens my sysadmin.

The close() method needs to set the 'done' flag to true immediately, then send a
final client socket connection to TelnetAppender to consume the last waiting
serverSocket.accept(), before closing the serverSocket.  Ir just get rid of the
log statement.

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