FW: a bug? of Log4J

[Yuji Takada <yu...@flab.fujitsu.co.jp>]

I have reported the bug of the log4j-v0.8.5b as in the following
email and Ceki have fixed it. However, this bug comes out again
in the current version of Log4J (jakarta-log4j-1.0.4). We are
wondering if the current version is on a different history from
log4j-v0.8.5b.

Anyway, this bug should be fixed. Should I report this to the bug
database? I am hesitating because this is not a new bug.

Regards,
Yuji

-----Original Message-----
From: cgu@fgwmail2.fujitsu.co.jp
[mailto:cgu@fgwmail2.fujitsu.co.jp]On Behalf Of Ceki Gulcu
Sent: Tuesday, October 31, 2000 12:54 AM
To: Yuji Takada
Cc: cgu@freesurf.ch
Subject: Re: a bug? of Log4J


Yuji Takada wrote:
>
> Dear Sir,
>
> we are planning to use log4j in our product and checking it for
this
> purpose. Then, we found a strange stuff in log4j.
>
> With log4j-v0.8.5b, we could not have any warning log in
Windows NT event
> log. We checked the source code and found that, for NT event,
Priority class
> defines the values as 0, 100, 200, ... while NTEventLogAppender
Class deals
> with these values as 0, 1, 2, ... Due to this different
definition, no
> warning log is put into NT event log. We are wondering if this
is a bug of
> log4j... In fact, if we changed the values as 0, 1, 2, 3, ...
in Priority
> class then all the events in NT event log look OK.
>
> We would appreciate very much if you look into this problem and
fix it. We
> know an obvious way to fix this problem but we think that you
must get the
> right and best way for this problem.

Thanks for the bug report. I'll fix it asap. Ceki

Re: FW: a bug? of Log4J

[Ceki Gülcü <cg...@urbanet.ch>]

Yuji,

I am embarrassed to say that it is a related but a different bug. However, 
it has been fixed in the version in our CVS rep. The log4j "history" is the 
same: the same name, the same authors, the same bugs... :-)

Cheers, Ceki

At 09:30 31.01.2001 +0900, you wrote:
>I have reported the bug of the log4j-v0.8.5b as in the following
>email and Ceki have fixed it. However, this bug comes out again
>in the current version of Log4J (jakarta-log4j-1.0.4). We are
>wondering if the current version is on a different history from
>log4j-v0.8.5b.
>
>Anyway, this bug should be fixed. Should I report this to the bug
>database? I am hesitating because this is not a new bug.
>
>Regards,
>Yuji
>
>-----Original Message-----
>From: cgu@fgwmail2.fujitsu.co.jp
>[mailto:cgu@fgwmail2.fujitsu.co.jp]On Behalf Of Ceki Gulcu
>Sent: Tuesday, October 31, 2000 12:54 AM
>To: Yuji Takada
>Cc: cgu@freesurf.ch
>Subject: Re: a bug? of Log4J
>
>
>Yuji Takada wrote:
> >
> > Dear Sir,
> >
> > we are planning to use log4j in our product and checking it for
>this
> > purpose. Then, we found a strange stuff in log4j.
> >
> > With log4j-v0.8.5b, we could not have any warning log in
>Windows NT event
> > log. We checked the source code and found that, for NT event,
>Priority class
> > defines the values as 0, 100, 200, ... while NTEventLogAppender
>Class deals
> > with these values as 0, 1, 2, ... Due to this different
>definition, no
> > warning log is put into NT event log. We are wondering if this
>is a bug of
> > log4j... In fact, if we changed the values as 0, 1, 2, 3, ...
>in Priority
> > class then all the events in NT event log look OK.
> >
> > We would appreciate very much if you look into this problem and
>fix it. We
> > know an obvious way to fix this problem but we think that you
>must get the
> > right and best way for this problem.
>
>Thanks for the bug report. I'll fix it asap. Ceki
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

----
Ceki Gülcü - Independent IT Consultant

av. de Rumine 5            Tel: ++41 21 351 23 15
CH-1005 Lausanne        e-mail: cgu@urbanet.ch  or
Switzerland                     ceki_gulcu@yahoo.com