Author: markt
Date: Thu Oct 3 12:55:20 2013
New Revision: 1528834
URL: http://svn.apache.org/r1528834
Log:
Remove method call that appears to be unnecessary and on rare occassions has
triggered a unit test failure.
Modified:
tomcat/trunk/java/org/apache/juli/ClassLoaderLogManager.java
Modified: tomcat/trunk/java/org/apache/juli/ClassLoaderLogManager.java
URL:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/juli/ClassLoaderLogManager.java?rev=1528834&r1=1528833&r2=1528834&view=diff
==============================================================================
--- tomcat/trunk/java/org/apache/juli/ClassLoaderLogManager.java (original)
+++ tomcat/trunk/java/org/apache/juli/ClassLoaderLogManager.java Thu Oct 3
12:55:20 2013
@@ -333,7 +333,11 @@ public class ClassLoaderLogManager exten
ClassLoader classLoader = thread.getContextClassLoader();
ClassLoaderLogInfo clLogInfo = getClassLoaderInfo(classLoader);
resetLoggers(clLogInfo);
- super.reset();
+ // Do not call super.reset(). It should be a NO-OP as all loggers
should
+ // have been registered via this manager. Very rarely a
+ // ConcurrentModificationException has been seen in the unit tests when
+ // calling super.reset() and that exception could cause the stop of a
+ // web application to fail.
}
/**
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
