Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
From: bugzilla@apache.org
To: log4j-dev@logging.apache.org
Subject: DO NOT REPLY [Bug 44109]  - Telnet Appender throws null pointers at
 log time when socket couldn't be opened
In-Reply-To: <bug-44109-31091@http.issues.apache.org/bugzilla/>
Message-Id: <20080117182057.AEEEE71426D@brutus.apache.org>
Date: Thu, 17 Jan 2008 10:20:57 -0800 (PST)

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


carnold@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED


------- Additional Comments From carnold@apache.org  2008-01-17 10:20 -------
One of the design goals of log4j 2.0 is to provide feedback of unexpected conditions.  Basically log4j 1.x's 
design was to hide all feedback on the health of the logging system from the application developer and 
what feedback was provided was sent to the console.

The null pointer in TelnetAppender.append however should have been checked, committed in rev 612911 
and 612914.

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

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