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 Frank-Olaf Lohmann - IS4 <Lo...@hhla.de> on 2004/11/08 11:20:13 UTC
Wtrlt: failure notice
Hi. This is the qmail-send program at apache.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<lo...@jakarta.apache.org>:
This list has moved: log4j-dev@logging.apache.org
--- Below this line is a copy of the message.
Return-Path: <lo...@hhla.de>
Received: (qmail 14019 invoked by uid 99); 8 Nov 2004 10:04:05 -0000
X-ASF-Spam-Status: No, hits=0.1 required=10.0
tests=HTML_60_70,HTML_MESSAGE
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from [217.110.121.167] (HELO mail1.hhla.de) (217.110.121.167)
by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 08 Nov 2004 02:03:59 -0800
Received: from [217.110.121.155] (helo=mail.hhla.de)
by mail1.hhla.de with esmtp (Exim 4.41)
id 1CR6NP-0007mP-JI
for log4j-dev@jakarta.apache.org; Mon, 08 Nov 2004 11:03:55 +0100
Received: from DOTMP-MTA by mail.hhla.de
with Novell_GroupWise; Mon, 08 Nov 2004 11:03:55 +0100
Message-Id: <s1...@mail.hhla.de>
X-Mailer: Novell GroupWise Internet Agent 6.5.2
Date: Mon, 08 Nov 2004 11:03:39 +0100
From: "Frank-Olaf Lohmann - IS4" <Lo...@hhla.de>
To: <lo...@jakarta.apache.org>
Subject: Closing TelnetAppender bombs with LogLog messages
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part89A94A6B.0__="
X-yoursite-MailScanner-Information: Please contact the ISP for more information
X-yoursite-MailScanner: Found to be clean
X-Virus-Checked: Checked
--=__Part89A94A6B.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hi,
I found that closing the TelnetAppender cause whole lot of messages
logged. All this messages are of the kind 'Encountered error while in
SocketHandler loop.'
This is not a bug but IMHO a flaw. It can be omitted easily by changing
one line of code and add another.
122a123
> done = true;
127d127
< done = true;
166c166,168
< LogLog.error("Encountered error while in SocketHandler
loop.", e);
---
> if(!done) {
> LogLog.error("Encountered error while in SocketHandler
loop.", e);
> }
It would be nice if this little change can find it's way to next
release.
regards
Frank-Olaf Lohmann
--=__Part89A94A6B.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2800.1226" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN-TOP: 2px; FONT: 8pt Tahoma; MARGIN-LEFT: 2px">
<DIV><FONT size=3D1>Hi,</FONT></DIV>
<DIV><FONT size=3D1></FONT> </DIV>
<DIV><FONT size=3D1>I found that closing the TelnetAppender cause whole =
lot of=20
messages logged. All this messages are of the kind 'Encountered error =
while in=20
SocketHandler loop.'</FONT></DIV>
<DIV><FONT size=3D1>This is not a bug but IMHO a flaw. It can be omitted =
easily by=20
changing one line of code and add another.</FONT></DIV>
<DIV> </DIV>
<DIV>122a123<BR>> done =3D=20
true;<BR>127d127<BR>< done =3D=20
true;<BR>166c166,168<BR><  =
; =20
LogLog.error("Encountered error while in SocketHandler loop.",=20
e);<BR>---<BR>> &nb=
sp; =20
if(!done)=20
{<BR>> =
=20
LogLog.error("Encountered error while in SocketHandler loop.",=20
e);<BR>> &nbs=
p; =20
}<BR></DIV>
<DIV><FONT size=3D1>It would be nice if this little change can find it's =
way to=20
next release.</FONT></DIV>
<DIV><FONT size=3D1></FONT> </DIV>
<DIV><FONT size=3D1>regards</FONT></DIV>
<DIV><FONT size=3D1>Frank-Olaf Lohmann</FONT></DIV>
<DIV><FONT size=3D1></FONT> </DIV></BODY></HTML>
--=__Part89A94A6B.0__=--
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org