log rotation error/bug
cantor.2 at osu.edu
Fri Dec 18 18:25:17 EST 2015
> 18-Dec-2015 15:10:03.992 INFO [Thread-77]
> Loading 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.
I'm not sure what that means. Uncaught exception or not, I don't know how that would cause the webapp to "stop" or what that would mean. But I'm sure that in that scenario there could be issues with the log because it inits the logging config in the webapp start sequence.
Seems like maybe two copies ended up running and grabbing the same file handles or got into some kind of race condition. I would tend to point the finger at Tomcat as the main source of trouble.
Did you happen to be using some kind of JNDI resource at the container level for the LDAP connection? Not sure if we handle that or not, I only know about the JDBC case.
More information about the users