[ 
https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646507#comment-13646507
 ] 

Remko Popma commented on LOG4J2-223:
------------------------------------

Olivier, I tried running archiva.
I could not get it to run (OutOfMemory on my 32bit PC at work), but I did see 
this:

2013-05-01 19:56:22,300 DEBUG property AsyncLoggerConfig.WaitStrategy=null <--- 
(1) Mixed Async Logger <asyncRoot/asyncLogger>
2013-05-01 19:56:22,300 DEBUG disruptor event handler uses SleepingWaitStrategy
2013-05-01 19:56:22,331 DEBUG No AsyncLoggerConfig.ExceptionHandler specified
2013-05-01 19:56:22,331 DEBUG Starting AsyncLoggerConfig disruptor with 
ringbuffer size 262144...
2013-05-01 19:56:22,347 DEBUG Reconfiguration completed
2013-05-01 19:56:22,347 DEBUG Using default SystemClock for timestamps
2013-05-01 19:56:22,347 DEBUG property AsyncLogger.WaitStrategy=null  <----(2) 
All Async Loggers (sysprop Log4jContextSelector)
2013-05-01 19:56:22,347 DEBUG disruptor event handler uses SleepingWaitStrategy
2013-05-01 19:56:22,394 DEBUG No AsyncLogger.ExceptionHandler specified
2013-05-01 19:56:22,394 DEBUG Starting AsyncLogger disruptor with ringbuffer 
size 262144...

Looks like you are using both Async Logger mechanisms together:
1) the log4j2.xml config has <asyncLogger> and <asyncRoot>    (and quite a few 
of them, good test case! )
2) in addition, /archiva/archiva-modules/archiva-web/archiva-webapp/pom.xml has 
this line:
            
<Log4jContextSelector>org.apache.logging.log4j.core.async.AsyncLoggerContextSelector</Log4jContextSelector>

This means you end up with 2 disruptors. You only need one.
The fix for LOG4J2-222 only works for (1). Can you try again after removing the 
AsyncLoggerContextSelector config from archiva-webapp/pom.xml ?
                
> IlliegalStateException thrown during Tomcat shutdown
> ----------------------------------------------------
>
>                 Key: LOG4J2-223
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-223
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0-beta5
>            Reporter: Ralph Goers
>            Assignee: Ralph Goers
>             Fix For: 2.0-beta6
>
>
> Apr 25, 2013 3:03:33 PM org.apache.catalina.core.StandardServer await
> INFO: A valid shutdown command was received via the shutdown port. Stopping 
> the Server instance.
> Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol pause
> INFO: Pausing ProtocolHandler ["http-nio-8080"]
> Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol pause
> INFO: Pausing ProtocolHandler ["ajp-nio-8009"]
> Apr 25, 2013 3:03:33 PM org.apache.catalina.core.StandardService stopInternal
> INFO: Stopping service Catalina
> Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol stop
> INFO: Stopping ProtocolHandler ["http-nio-8080"]
> Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol stop
> INFO: Stopping ProtocolHandler ["ajp-nio-8009"]
> Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol destroy
> INFO: Destroying ProtocolHandler ["http-nio-8080"]
> Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol destroy
> INFO: Destroying ProtocolHandler ["ajp-nio-8009"]
> Apr 25, 2013 3:03:33 PM org.apache.catalina.loader.WebappClassLoader loadClass
> INFO: Illegal access: this web application instance has been stopped already. 
>  Could not load org.apache.logging.log4j.core.config.NullConfiguration.  The 
> eventual following stack trace is caused by an error thrown for debugging 
> purposes as well as to attempt to terminate the thread which caused the 
> illegal access, and has no functional impact.
> java.lang.IllegalStateException
>       at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1351)
>       at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310)
>       at 
> org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:171)
>       at 
> org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:389)
> Exception in thread "Thread-18" java.lang.NoClassDefFoundError: 
> org/apache/logging/log4j/core/config/NullConfiguration
>       at 
> org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:171)
>       at 
> org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:389)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.logging.log4j.core.config.NullConfiguration
>       at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1465)
>       at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310)
>       ... 2 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to