I've opened:
https://issues.apache.org/jira/browse/LOG4J2-571
and just closed it.
The reason for the CPU thrashing was that it was the AsyncLoggerConfig
thread that was going nuts. That needs the property:
-DAsyncLoggerConfig.WaitStrategy=Block
to be set, not:
-DAsyncLogger.WaitStrategy
[mailto:chrisgw...@gmail.com]
Envoyé : mercredi 19 mars 2014 11:14
À : dev@archiva.apache.org
Objet : Re: CPU Thrashing
I've opened:
https://issues.apache.org/jira/browse/LOG4J2-571
and just closed it.
The reason for the CPU thrashing was that it was the AsyncLoggerConfig
thread that was going nuts
and/or
-DAsyncLoggerConfig.WaitStrategy=Block )
Maybe better alternative.
Regards
Eric
-Message d'origine-
De : Chris Graham [mailto:chrisgw...@gmail.com]
Envoyé : mercredi 19 mars 2014 11:14
À : dev@archiva.apache.org
Objet : Re: CPU Thrashing
I've opened:
https
On 14 October 2013 11:13, Chris Graham chrisgw...@gmail.com wrote:
Hi Olivier.
I'll try to have a look at that one soon.
Oddly enough, here is a log4j.xml that is 'broken', in that it is valid XML
(from what I can see) however, there is ZERO output, and the CPU usage is
1%, which is what it
Hi
I believe trunk with the last log4j2 beta version should fix that.
Cheers,
--
Olivier
On Oct 11, 2013 9:33 PM, Chris Graham chrisgw...@gmail.com wrote:
Hi All.
I've been having no end of fun with the M4 release of Archiva under WAS 8.5
on AIX (64 bit).
With archiva doing nothing (ie not
Hi Olivier.
I'll try to have a look at that one soon.
Oddly enough, here is a log4j.xml that is 'broken', in that it is valid XML
(from what I can see) however, there is ZERO output, and the CPU usage is
1%, which is what it shouldbe.
Is this an issue with the way that log4j parses (and fails
Hi All.
I've been having no end of fun with the M4 release of Archiva under WAS 8.5
on AIX (64 bit).
With archiva doing nothing (ie not processing new releases or serving any
requests from any remote maven's), it is consuming anywhere from 40-95% CPU.
I managed to get the log4j2.xml file in a
