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 Kurt Lehrke <Ku...@jda.com> on 2014/03/25 18:14:28 UTC
RE: log4j2 rc1 bug
Hey everyone,
Did you guys ever get a chance to look into this? If it's a confirmed bug, we can open a jira for you with the appropriate information. Currently, we're on beta 9 unable to move to RC1 because of it.
Thanks,
Kurt
From: John Bedalov
Sent: Wednesday, March 19, 2014 4:01 PM
To: log4j-dev@logging.apache.org
Cc: Kurt Lehrke
Subject: log4j2 rc1 bug
Log4j Team,
Attached you will find a small project that reproduces a bug we have identified when moving from log4j2 beta 9 to log4j2 RC1.
The bug occurs when trying to use our own converter. In beta the results were stable and predictable. In RC1, this output is only generated about 30% of the time
2014-03-19 15:34:28,491 ERROR [1] tests.TestLogger (TestLogger.java:27) - running configuration: C:\dev\log4j2-testing\log4j2.xml
2014-03-19 15:34:28,492 INFO [1] tests.TestLogger (TestLogger.java:29) - info level
2014-03-19 15:34:28,493 ERROR [1] tests.TestLogger (TestLogger.java:30) - error level
Using RC1, we get this output about 70% of the time (and never with beta)
2014-03-19 15:43:03,797 ERROR Unrecognized format specifier [T]
2014-03-19 15:43:03,798 ERROR Unrecognized conversion specifier [T] starting at position 11 in conversion pattern.
2014-03-19 15:43:03,806 ERROR [%T] tests.TestLogger (TestLogger.java:27) - running configuration: C:\dev\log4j2-testing\log4j2.xml
2014-03-19 15:43:03,808 INFO [%T] tests.TestLogger (TestLogger.java:29) - info level
2014-03-19 15:43:03,808 ERROR [%T] tests.TestLogger (TestLogger.java:30) - error level
Let me know if you have any questions about the attached code or the issue.
Thanks,
John Bedalov | Software Engineer
JDA - The Supply Chain Company
Waukesha, WI, USA
Office: (262) 317-2851
Worldwide +1 (480) 308-3000
John.Bedalov@jda.com<ma...@jda.com>
Visit jda.com
<http://www.jda.com/?elq=f04579b9dc09412fbdee7cee26acdd55>[cid:image001.jpg@01CDFA42.E84AE3A0]
Viva JDA! Join us at JDA FOCUS April 27-30 in Vegas! Register now at jda.com/FOCUS<http://now.jda.com/2014-FOCUS-TextLink.html>
Re: log4j2 rc1 bug
Posted by Matt Sicker <bo...@gmail.com>.
Now that you mention it, I usually see the socket server tests fail on my
computer, but the tests themselves still pass for some reason. It's
actually rather confusing sometimes whether or not the tests succeed based
on the output (except for when an informative message is part of the stack
trace like "Always fail").
On 25 March 2014 12:14, Kurt Lehrke <Ku...@jda.com> wrote:
> Hey everyone,
>
>
>
> Did you guys ever get a chance to look into this? If it’s a confirmed
> bug, we can open a jira for you with the appropriate information.
> Currently, we’re on beta 9 unable to move to RC1 because of it.
>
>
>
> Thanks,
>
> Kurt
>
>
>
> *From:* John Bedalov
> *Sent:* Wednesday, March 19, 2014 4:01 PM
> *To:* log4j-dev@logging.apache.org
> *Cc:* Kurt Lehrke
> *Subject:* log4j2 rc1 bug
>
>
>
> Log4j Team,
>
>
>
> Attached you will find a small project that reproduces a bug we have
> identified when moving from log4j2 beta 9 to log4j2 RC1.
>
>
>
> The bug occurs when trying to use our own converter. In beta the results
> were stable and predictable. In RC1, this output is only generated about
> 30% of the time
>
>
>
> 2014-03-19 15:34:28,491 ERROR [1] tests.TestLogger (TestLogger.java:27) -
> running configuration: C:\dev\log4j2-testing\log4j2.xml
>
> 2014-03-19 15:34:28,492 INFO [1] tests.TestLogger (TestLogger.java:29) -
> info level
>
> 2014-03-19 15:34:28,493 ERROR [1] tests.TestLogger (TestLogger.java:30) -
> error level
>
>
>
> Using RC1, we get this output about 70% of the time (and never with beta)
>
>
>
> 2014-03-19 15:43:03,797 ERROR Unrecognized format specifier [T]
>
> 2014-03-19 15:43:03,798 ERROR Unrecognized conversion specifier [T]
> starting at position 11 in conversion pattern.
>
> 2014-03-19 15:43:03,806 ERROR [%T] tests.TestLogger (TestLogger.java:27) -
> running configuration: C:\dev\log4j2-testing\log4j2.xml
>
> 2014-03-19 15:43:03,808 INFO [%T] tests.TestLogger (TestLogger.java:29) -
> info level
>
> 2014-03-19 15:43:03,808 ERROR [%T] tests.TestLogger (TestLogger.java:30) -
> error level
>
>
>
> Let me know if you have any questions about the attached code or the issue.
>
>
>
> Thanks,
>
> *John Bedalov* | Software Engineer
>
>
> *JDA - The Supply Chain Company *Waukesha, WI, USA
>
> Office: (262) 317-2851
>
> Worldwide +1 (480) 308-3000
>
> John.Bedalov@jda.com
>
> Visit jda.com
>
> <http://www.jda.com/?elq=f04579b9dc09412fbdee7cee26acdd55>[image:
> cid:image001.jpg@01CDFA42.E84AE3A0]
>
>
>
> *Viva JDA! Join us at JDA FOCUS April 27-30 in Vegas! Register now at
> jda.com/FOCUS <http://now.jda.com/2014-FOCUS-TextLink.html>*
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
--
Matt Sicker <bo...@gmail.com>