[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[
https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661373#comment-13661373
]
Nick Williams commented on LOG4J2-223:
--
With {{status=DEBUG}}:
{noformat}2013-05-18 10:10:54,533 DEBUG Generated plugins in 0.28800 seconds
2013-05-18 10:10:54,533 DEBUG Generated plugins in 0.13200 seconds
2013-05-18 10:10:54,534 DEBUG Generated plugins in 0.12700 seconds
2013-05-18 10:10:54,534 DEBUG Generated plugins in 0.13100 seconds
2013-05-18 10:10:54,535 DEBUG Generated plugins in 0.13500 seconds
2013-05-18 10:10:54,535 DEBUG Generated plugins in 0.12700 seconds
2013-05-18 10:10:54,536 DEBUG Generated plugins in 0.12900 seconds
2013-05-18 10:10:54,536 DEBUG Generated plugins in 0.12400 seconds
2013-05-18 10:10:54,536 DEBUG Generated plugins in 0.12100 seconds
2013-05-18 10:10:54,537 DEBUG Generated plugins in 0.12600 seconds
2013-05-18 10:10:54,537 DEBUG Generated plugins in 0.12000 seconds
2013-05-18 10:10:54,538 DEBUG Generated plugins in 0.12300 seconds
2013-05-18 10:10:54,538 DEBUG Generated plugins in 0.15800 seconds
2013-05-18 10:10:54,539 DEBUG Generated plugins in 0.15800 seconds
2013-05-18 10:10:54,539 DEBUG Generated plugins in 0.12700 seconds
2013-05-18 10:10:54,540 DEBUG Generated plugins in 0.12800 seconds
2013-05-18 10:10:54,548 DEBUG Calling createLayout on class
org.apache.logging.log4j.core.layout.PatternLayout for element PatternLayout
with params(pattern=%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n,
Configuration(C:\Users\Nicholas\Desktop\Logging-Integration\target\logging-integration-1.0.0.SNAPSHOT\WEB-INF\classes\log4j2.xml),
null, charset=null, suppressExceptions=null)
2013-05-18 10:10:54,549 DEBUG Generated plugins in 0.19700 seconds
2013-05-18 10:10:54,551 DEBUG Calling createAppender on class
org.apache.logging.log4j.core.appender.ConsoleAppender for element Console with
params(PatternLayout(%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n),
null, target=SYSTEM_OUT, name=Console, follow=null,
suppressExceptions=null)
2013-05-18 10:10:54,551 DEBUG Jansi is not installed
2013-05-18 10:10:54,552 DEBUG Calling createLayout on class
org.apache.logging.log4j.core.layout.PatternLayout for element PatternLayout
with params(pattern=%d{HH:mm:ss.SSS} [%t] %X{id} %X{username} %-5level %c{36}
%l: %msg%n,
Configuration(C:\Users\Nicholas\Desktop\Logging-Integration\target\logging-integration-1.0.0.SNAPSHOT\WEB-INF\classes\log4j2.xml),
null, charset=null, suppressExceptions=null)
2013-05-18 10:10:54,553 DEBUG Calling createPolicy on class
org.apache.logging.log4j.core.appender.rolling.SizeBasedTriggeringPolicy for
element SizeBasedTriggeringPolicy with params(size=10 MB)
2013-05-18 10:10:54,554 DEBUG Calling createPolicy on class
org.apache.logging.log4j.core.appender.rolling.CompositeTriggeringPolicy for
element Policies with
params(policies={SizeBasedTriggeringPolicy(size=10485760)})
2013-05-18 10:10:54,555 DEBUG Calling createStrategy on class
org.apache.logging.log4j.core.appender.rolling.DefaultRolloverStrategy for
element DefaultRolloverStrategy with params(max=4, min=1, fileIndex=null,
Configuration(C:\Users\Nicholas\Desktop\Logging-Integration\target\logging-integration-1.0.0.SNAPSHOT\WEB-INF\classes\log4j2.xml))
2013-05-18 10:10:54,557 DEBUG Calling createAppender on class
org.apache.logging.log4j.core.appender.RollingFileAppender for element
RollingFile with params(fileName=../logs/application.log,
filePattern=../logs/application-%d{MM-dd-}-%i.log, append=null,
name=WroxFileAppender, bufferedIO=null, immediateFlush=null,
Policies(CompositeTriggeringPolicy{SizeBasedTriggeringPolicy(size=10485760)}),
DefaultRolloverStrategy(DefaultRolloverStrategy(min=1, max=4)),
PatternLayout(%d{HH:mm:ss.SSS} [%t] %X{id} %X{username} %-5level %c{36} %l:
%msg%n), null, suppressExceptions=null, advertise=null,
advertiseURI=null,
Configuration(C:\Users\Nicholas\Desktop\Logging-Integration\target\logging-integration-1.0.0.SNAPSHOT\WEB-INF\classes\log4j2.xml))
2013-05-18 10:10:54,561 DEBUG Starting RollingFileManager
../logs/application.log
2013-05-18 10:10:54,563 DEBUG Generated plugins in 0.18300 seconds
2013-05-18 10:10:54,565 DEBUG Calling createAppenders on class
org.apache.logging.log4j.core.config.plugins.AppendersPlugin for element
appenders with params(appenders={Console, WroxFileAppender})
2013-05-18 10:10:54,565 DEBUG Generated plugins in 0.13300 seconds
2013-05-18 10:10:54,566 DEBUG Calling createAppenderRef on class
org.apache.logging.log4j.core.config.AppenderRef for element appender-ref with
params(ref=Console, level=null, null)
2013-05-18 10:10:54,567 DEBUG Calling createLogger on class
org.apache.logging.log4j.core.config.LoggerConfig$RootLogger for element root
with params(additivity=null, level=warn, includeLocation=null,
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661447#comment-13661447 ] Remko Popma commented on LOG4J2-223: I was unable to reproduce this issue on Apache Tomcat/7.0.40 or Apache Tomcat/6.0.36 (on Windows 7 (64b), Java 1.7.0_11 64bit). Steps to reproduce: # install Tomcat # cd to TOMCAT_HOME/bin # run startup.bat # drop attached file logging-integration-1.0.0.SNAPSHOT.war into TOMCAT_HOME/webapps # (there seems to be an extra directory named logging-integration-1.0.0.SNAPSHOT inside the WAR file, so pull the contents of TOMCAT_HOME/webapps/logging-integration-1.0.0.SNAPSHOT/logging-integration-1.0.0.SNAPSHOT into TOMCAT_HOME/webapps/logging-integration-1.0.0.SNAPSHOT) # open http://localhost:8080/logging-integration-1.0.0.SNAPSHOT/ in browser ## (result on Tomcat 6) 404 - /logging-integration-1.0.0.SNAPSHOT/files is not available ## (result on Tomcat 7) 404 - /logging-integration-1.0.0.SNAPSHOT/ is not available # run shutdown.bat # Tomcat stops without any issues Sorry Nick, I am giving up on this one. 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 Priority: Critical Fix For: 2.0-beta7 Attachments: logging-integration-1.0.0.SNAPSHOT.war, Logging-Integration.zip 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[
https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661487#comment-13661487
]
Remko Popma commented on LOG4J2-223:
with the above steps I was able to reproduce the issue. (I only tried Tomcat 7,
btw.)
{code}
5 19, 2013 11:12:11 AM 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:1600)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:199)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:418)
Exception in thread Thread-36 java.lang.NoClassDefFoundError:
org/apache/logging/log4j/core/config/NullConfiguration
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:199)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:418)
Caused by: java.lang.ClassNotFoundException:
org.apache.logging.log4j.core.config.NullConfiguration
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1714)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)
... 2 more
5 19, 2013 11:12:11 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler [ajp-apr-8009]
5 19, 2013 11:12:11 AM org.apache.catalina.core.StandardService stopInternal
{code}
Looks like Catalina's WebappClassLoader won't allow a web application to load
new classes after it has been stopped.
The problem seems to be the code here:
{code}
public void stop() {
configLock.lock();
try {
if (status == Status.STOPPED) {
return;
}
status = Status.STOPPING;
if (shutdownThread != null) {
Runtime.getRuntime().removeShutdownHook(shutdownThread);
shutdownThread = null;
}
Configuration prev = config;
config = new NullConfiguration(); // -- Tomcat won't let us do this
updateLoggers();
prev.stop();
externalContext = null;
status = Status.STOPPED;
} finally {
configLock.unlock();
}
}
{code}
Here is what I tried: at the top of LoggerContext, declare a static field
holding an instance of NullConfiguration.
{code}
// LOG4J2-223 cannot load new class during stop() in web apps, so load this up
front
private static final NullConfiguration NULL_CONFIGURATION = new
NullConfiguration();
{code}
Then, in the stop() method, instead of creating a new NullConfiguration, return
the pre-loaded instance:
{code}
status = Status.STOPPING;
if (shutdownThread != null) {
Runtime.getRuntime().removeShutdownHook(shutdownThread);
shutdownThread = null;
}
Configuration prev = config;
config = NULL_CONFIGURATION;
updateLoggers();
prev.stop();
externalContext = null;
status = Status.STOPPED;
{code}
To test this, I unzipped the log4j-223.war file and replaced these files:
log4j-api-2.0-beta6.jar
log4j-core-2.0-beta6.jar
log4j-jcl-2.0-beta6.jar
log4j-slf4j-impl-2.0-beta6.jar
log4j-taglib-2.0-beta6.jar
with these freshly built files:
log4j-api-2.0-beta7-SNAPSHOT.jar
log4j-core-2.0-beta7-SNAPSHOT.jar
log4j-jcl-2.0-beta7-SNAPSHOT.jar
log4j-slf4j-impl-2.0-beta7-SNAPSHOT.jar
log4j-taglib-2.0-beta7-SNAPSHOT.jar
Then I followed the same steps as Nick described above to check the result.
Opening http://localhost:8080/log4j-223a/ gave (I actually got a Japanese error
message but this is my rough translation):
500 - /index.jsp (line: 1, column: 1) absolute URI:
http://logging.apache.org/log4j/tld/log cannot be resolved in(?) web.xml or the
deployed jar for this application
I think this is related to the JSP Taglib, here is the stack trace for
completeness:
{code}
org.apache.jasper.JasperException: /index.jsp (line: 1, column: 1) absolute
URI:
http://logging.apache.org/log4j/tld/log cannot be resolved
in(?)
web.xml or the deployed jar for this application
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:42)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:443)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:89)
org.apache.jasper.compiler.Parser.processIncludeDirective(Parser.java:324)
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[
https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661488#comment-13661488
]
Remko Popma commented on LOG4J2-223:
The 500 error above is probably not related to Taglib. It also occurred after
replacing the logging.jsp with a simple Hello world containing only HTML tags.
Not sure if this is related, but the console also shows this:
{code}
5 19, 2013 1:18:36 午後 org.apache.jasper.compiler.TldLocationsCache tldScanJar
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug
logging for this logger for a complete list of JARs that were scanned
but no TLDs were found in them. Skipping unneeded JARs during scanning can
improve startup time and JSP compilation time.
{code}
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
Priority: Critical
Fix For: 2.0-beta7
Attachments: log4j-223.war
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: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[
https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661489#comment-13661489
]
Nick Williams commented on LOG4J2-223:
--
Try going to http://localhost:8080/log4j-223a/files directly instead of
http://localhost:8080/log4j-223a/.
Cause: log4j-taglib*.jar contains a TLD (Tag Library Descriptor) used in the
JSPs. The container must scan this JAR to pick up the TLD. However, since Log4j
has never had a tag library until now, Tomcat has an exclusion built in that
says not to scan log4j*.jar files for tag libraries (for which I have filed a
bug, https://issues.apache.org/bugzilla/show_bug.cgi?id=54770). In my local
Tomcat install, I removed the log4j*.jar exclusion from catalina.properties.
You can either do the same, or go to http://localhost:8080/log4j-223a/files
directly to skip all JSPs and therefore avoid TLD-loading errors.
This is unrelated to the issue at hand, but is the cause of the new errors you
saw. Just go to http://localhost:8080/log4j-223a/files directly (or remove the
log4j*.jar exclusion from TOMCAT_HOME/conf/catalina.properties) to isolate the
IllegalStateException behavior.
It looks like your change may fix the error being displayed, but I don't think
it resolves the underlying issue. The underlying issue appears to be a memory
leak. By registering a shutdown hook, Log4j creates a thread with classes
loaded in the servlet context class loader but held on to by the JVM. When
Tomcat undeploys the application, the garbage collector will be unable to
collect the servlet context class loader and any classes it loaded because of
this. If you redeploy and undeploy the application several times, you will
eventually get an {{OutOfMemoryError: perm gen space}} exception.
What is this code trying to accomplish? Why are we registering a shutdown hook
here? I question the necessity of this code, and its existence is creating a
dangerous situation for web applications.
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
Priority: Critical
Fix For: 2.0-beta7
Attachments: log4j-223.war
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
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[
https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661262#comment-13661262
]
Nick Williams commented on LOG4J2-223:
--
In the latest 2.0-beta7-SNAPSHOT, this is still not fixed:
{noformat}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:201)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:427)
Exception in thread Thread-19 java.lang.NoClassDefFoundError:
org/apache/logging/log4j/core/config/NullConfiguration
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:201)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:427)
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{noformat}
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
Priority: Critical
Fix For: 2.0-beta7
Attachments: logging-integration-1.0.0.SNAPSHOT.war,
Logging-Integration.zip
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:
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661266#comment-13661266 ] Remko Popma commented on LOG4J2-223: Haven't had a chance. Have been making long hours at work. I don't think I'll be able to this weekend. I don't even have Tomcat set up yet... Btw, could you provide some more details on versions and stuff? Java version, Tomcat version? Any command line options? I'm not 100% sure but you are not using Async Loggers, are you? Are you using another ContextSelector? Also, not sure if relevant, but are you using the JSP TagLib? 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 Priority: Critical Fix For: 2.0-beta7 Attachments: logging-integration-1.0.0.SNAPSHOT.war, Logging-Integration.zip 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661268#comment-13661268 ] Nick Williams commented on LOG4J2-223: -- Java 1.8.0-ea-b88 Tomcat 8.0-SNAPSHOT (r1478984) No special command-line options. I am not using Async Loggers. I am not using another ContextSelector. I /am/ using the Tag Library but I get this error even if I don't go to any JSPs, so I don't think that's it. I'd encourage you to try to duplicate this on Java 7 / Tomcat 7 before bothering trying to replicate my setup. 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 Priority: Critical Fix For: 2.0-beta7 Attachments: logging-integration-1.0.0.SNAPSHOT.war, Logging-Integration.zip 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661289#comment-13661289 ] Remko Popma commented on LOG4J2-223: Thanks. Unexpected family circumstances just came up and I won't have access to a PC today, maybe this weekend. Only iPhone. Could you paste the output of StatusLogger debug output here? 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 Priority: Critical Fix For: 2.0-beta7 Attachments: logging-integration-1.0.0.SNAPSHOT.war, Logging-Integration.zip 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652715#comment-13652715 ] Nick Williams commented on LOG4J2-223: -- I still get this when shutting down Tomcat using Log4j2 beta6. This issue is not fixed. 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:199) at org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:418) Exception in thread Thread-13 java.lang.NoClassDefFoundError: org/apache/logging/log4j/core/config/NullConfiguration at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:199) at org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:418) 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 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail:
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652730#comment-13652730 ] Remko Popma commented on LOG4J2-223: Darn! Hmm... I guess I need help to reproduce this issue. (It worked when Olivier and I tested.) Would it be possible to attach a small case that demonstrates the issue? 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13647340#comment-13647340 ] Olivier Lamy (*$^¨%`£) commented on LOG4J2-223: --- Thanks Dude ! 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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: Log4jContextSelectororg.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
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646524#comment-13646524 ] Remko Popma commented on LOG4J2-223: Thanks, that helped. I can now see one disruptor being started, followed by lots of archiva startup logs (cute banner btw)... When I press Ctrl-C, I get the same problem that Ralph fixed in LOG4J2-222. How do I make aptiva use my latest build of log4j2-XX-beta6-SNAPSHOT ? 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646527#comment-13646527 ] Olivier Lamy (*$^¨%`£) commented on LOG4J2-223: --- that's already the case :-) mb-olamy:archiva olamy$ grep 'log4j.version' pom.xml log4j.version2.0-beta6-SNAPSHOT/log4j.version You must install locally 2.0-beta6-SNAPSHOT (not sure snapshots for repository.a.o are deployed ?) 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646529#comment-13646529 ] Remko Popma commented on LOG4J2-223: That does not match what I'm seeing: Ctrl-C 2013-05-01 20:57:08,487 DEBUG Generated plugins in 0.10057 seconds 2013-05-01 20:57:08,487 DEBUG Jansi is not installed 2013-05-01 20:57:08,487 DEBUG Reconfiguration started for context Default --- problem 2 caused by problem 1 below 2013/05/01 20:57:08 org.apache.coyote.AbstractProtocol pause 情報: Pausing ProtocolHandler [http-bio-9091] 2013-05-01 20:57:08,519 DEBUG Generated plugins in 0.08660 seconds ... 2013-05-01 20:57:08,550 DEBUG Reconfiguration completed Exception in thread Thread-3 java.lang.IllegalStateException: Shutdown in progress at java.lang.ApplicationShutdownHooks.add(ApplicationShutdownHooks.java:39) at java.lang.Runtime.addShutdownHook(Runtime.java:192) at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:150) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:84) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:34) at org.apache.logging.log4j.LogManager.getContext(LogManager.java:138) PROBLEM 1 *** at org.apache.logging.log4j.core.async.AsyncLoggerConfig.stopFilter(AsyncLoggerConfig.java:132) at org.apache.logging.log4j.core.config.BaseConfiguration.stop(BaseConfiguration.java:136) at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:172) at org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:389) the line marked with PROBLEM 2 should not happen with the latest 2.0-beta6-SNAPSHOT: that call to LogManager.getContext was commented out... 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:
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646530#comment-13646530 ] Remko Popma commented on LOG4J2-223: ok I will try to replace the files in the local maven repo with my last build 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646532#comment-13646532 ] Olivier Lamy (*$^¨%`£) commented on LOG4J2-223: --- sure. mvn clean install (in log4j2 must do that :-)) 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[
https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646566#comment-13646566
]
Remko Popma commented on LOG4J2-223:
Phew. I can now reproduce the problem (at least very similar):
Ctrl-C
2013-05-01 21:53:04,093 DEBUG Shutting down OutputStreamManager SYSTEM_OUT
2013-05-01 21:53:04,093 DEBUG Shutting down FastRollingFileManager
D:\data\workspace-4.2.1\archiva\archiva-modules\archi
va-web\archiva-webapp\target/appserver-base/logs/archiva.log
2013/05/01 21:53:04 org.apache.coyote.AbstractProtocol pause
情報: Pausing ProtocolHandler [http-bio-9091]
Exception in thread Thread-3 java.lang.NullPointerException
at
org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper.shutdown(AsyncLoggerConfigHelper.java:227)
at
org.apache.logging.log4j.core.async.AsyncLoggerConfig.stopFilter(AsyncLoggerConfig.java:137)
at
org.apache.logging.log4j.core.config.BaseConfiguration.stop(BaseConfiguration.java:148)
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:201)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:418)
I suspect that the ShutdownThread runs after the Disruptor has already been
shut down in the main application thread.
The shutdown() code does not check if the static field holding the Disruptor
has already been set to null.
The fix is:
AsyncLoggerConfigHelper.shutdown() line 222:
CURRENT:
DisruptorLog4jEventWrapper temp = disruptor;
FIXED:
DisruptorLog4jEventWrapper temp = disruptor;
if (temp == null) { return; }
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: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646629#comment-13646629 ] Remko Popma commented on LOG4J2-223: Fixed in revision 1478040. I'll re-test tomorrow. Olivier, could you also take a look if you have time? 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13647130#comment-13647130 ] Remko Popma commented on LOG4J2-223: Tested and looks good. Archiva/Tomcat now shuts down cleanly on Ctrl-C. ... 情報: Starting ProtocolHandler [http-bio-9091] Ctrl-C 2013-05-02 09:29:06,786 DEBUG Shutting down OutputStreamManager SYSTEM_OUT 2013-05-02 09:29:06,786 DEBUG Shutting down FastRollingFileManager D:\data\workspace-4.2.1\archiva\archiva-modules\archi va-web\archiva-webapp\target/appserver-base/logs/archiva.log Terminate batch job (Y/N)? y D:\data\workspace-4.2.1\archiva 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645323#comment-13645323 ] Ralph Goers commented on LOG4J2-223: The flume-remote sample web app had this problem and was used to debug and resolve it. Oliver, can you test the latest code and verify that it fixes the problem you are seeing? 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645482#comment-13645482 ] Olivier Lamy (*$^¨%`£) commented on LOG4J2-223: --- [~ralph.go...@dslextreme.com] with r1477565 build locally I still have the issue. ^C2013-04-30 21:29:07,714 DEBUG Shutting down OutputStreamManager SYSTEM_OUT 2013-04-30 21:29:07,714 DEBUG Shutting down FastRollingFileManager /Users/olamy/dev/tests/archiva-appserver-base-test/logs/archiva.log Exception in thread Thread-6 java.lang.NullPointerException at org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper.shutdown(AsyncLoggerConfigHelper.java:227) at org.apache.logging.log4j.core.async.AsyncLoggerConfig.stopFilter(AsyncLoggerConfig.java:137) at org.apache.logging.log4j.core.config.BaseConfiguration.stop(BaseConfiguration.java:148) at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:201) at org.apache.logging.log4j.core.async.AsyncLoggerContext.stop(AsyncLoggerContext.java:57) at org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:418) 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645244#comment-13645244 ] Olivier Lamy (*$^¨%`£) commented on LOG4J2-223: --- If you need a sample project, I have similar issue with archiva project. svn co https://svn.apache.org/repos/asf/archiva/trunk/ archiva-trunk cd archiva-trunk sh ./t7.sh when tomcat running just use ctrl+c 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645268#comment-13645268 ] Remko Popma commented on LOG4J2-223: Thanks Olivier! I'll take a look when I get home. 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643869#comment-13643869 ] Nick Williams commented on LOG4J2-223: -- I guess you needed me to file a bug, huh? :-) Do you still need me to provide a sample project? Say the word. I've got it zipped up and can attach it on request. By the way, misspelling in the bug title. IlliegalStateException should be IllegalStateException. 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: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
