logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 44834] New: SimpleSocketServer looses buffered logs, produces spurious error on exit.
Date Thu, 17 Apr 2008 17:51:12 GMT

           Summary: SimpleSocketServer looses buffered logs, produces
                    spurious error on exit.
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Other
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: bernard.stumpf@verizon.net

Running SimpleSocketServer.java receiving logs from other nodes, configured via
XML, using RollingFileAppender with "BufferedIO" value="true", "BufferSize"
value="65536", upon socket close from the sending side the buffered logs are

Since SimpleSocketServer is a main program it is responsible for calling
LogManager::shutdown() as stated in the log4j documentation.

The lost logs problem is easily corrected by reconfiguring to do "BufferedIO"
value="false", but that defeats the performance purpose of buffering on the
server side.

The spurious error on exit was:

2008-04-15 18:16:19,410 [Thread-0] INFO  org.apache.log4j.net.SocketNode
(org.apache.log4j.net.SocketNode.run(SocketNode.java:89)) - Caught
java.io.EOFException closing conneciton.

Note also the misspelled "conneciton" in SocketNode.java (in three places)

Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message