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 2004/09/10 14:45:55 UTC

DO NOT REPLY [Bug 31158] New: - 2004-09-09 multiline changes not very well documented and break logging

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

http://issues.apache.org/bugzilla/show_bug.cgi?id=31158

2004-09-09 multiline changes not very well documented and break logging

           Summary: 2004-09-09 multiline changes not very well documented
                    and break logging
           Product: Log4j
           Version: 1.3alpha
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: chainsaw
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: iheino+l4j.ack5789@cc.hut.fi


There seems to be no documentation on what the multiline message support 
considers multiline. A file with 50000 log messages loaded fine before the 
yesterday's changes, today it shows only first couple messages.Some of the log 
messages were interpreted as part of throwable too. Maybe it's trying to fit 
50000+ lines in a single throwable and not showing the message before it thinks 
it has reached the end?

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