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/05/18 10:29:59 UTC

DO NOT REPLY [Bug 29058] New: - NullPointerException from XMLSocketReceiver when receiving old-format events

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

NullPointerException from XMLSocketReceiver when receiving old-format events

           Summary: NullPointerException from XMLSocketReceiver when
                    receiving old-format events
           Product: Log4j
           Version: 1.3alpha
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: chainsaw
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: apache@asgeirnilsen.com


One component generated old-style log4j:event data due to multiple versions in 
classpaths (using the "category" attribute instead of "logger").

Chainsaw got NullPointerExceptions when attempting to parse these entries, 
closing the Receiver.  A somewhat more fail-safe behaviour would be appreciated.

As a side note, there is little consistency as to where error messages appear.  
Sometimes, Chainsaw openes a separate "-" tab displaying the errors as log 
events, sometimes System.out gets it, and sometimes the "ChainsawCentral" pane 
gets it.

The version I use was checked out from CVS on May 12th, 2004.

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