log rotation error/bug

[Jeffrey Eaton]

I also just found, in tomcat's catalina.out, several instances of:

18-Dec-2015 15:10:03.992 INFO [Thread-77] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load [org.ldaptive.provider.jndi.NamingExceptionUtils]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [org.ldaptive.provider.jndi.NamingExceptionUtils]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
	at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1354)
	at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1340)
	at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1205)
	at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1166)
	at org.ldaptive.provider.jndi.JndiConnection.processNamingException(JndiConnection.java:752)
	at org.ldaptive.provider.jndi.JndiConnection_JndiSearchIterator.initialize(JndiConnection.java:888)
	at org.ldaptive.provider.jndi.JndiConnection.search(JndiConnection.java:533)
	at org.ldaptive.SearchOperation.executeSearch(SearchOperation.java:119)
	at org.ldaptive.SearchOperation.invoke(SearchOperation.java:101)
	at org.ldaptive.SearchOperation.invoke(SearchOperation.java:28)
	at org.ldaptive.AbstractOperation.execute(AbstractOperation.java:142)
	at org.ldaptive.pool.SearchValidator.validate(SearchValidator.java:97)
	at org.ldaptive.pool.SearchValidator.validate(SearchValidator.java:34)
	at org.ldaptive.pool.AbstractPool.validate(AbstractPool.java:223)
	at org.ldaptive.pool.AbstractConnectionPool.validate(AbstractConnectionPool.java:805)
	at org.ldaptive.pool.AbstractConnectionPool_3.run(AbstractConnectionPool.java:308)
	at java.util.concurrent.Executors_RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at java.util.concurrent.ScheduledThreadPoolExecutor_ScheduledFutureTask.access_301(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor_ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor_Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)


Curiouser and curiouser.  I wonder if the threads getting killed tickled some bug in the logback code.

-jeaton