org.apache.catalina.loader.WebappClassLoaderBase loadClass,Could not load org.apache.zookeeper.Clien

 

1、错误日志

tomcat的日志中报的错误，具体原因未知，网络搜索有的说是zookeeper连接数太多导致连接失败导致的

Jul 20, 2020 12:00:00 AM org.apache.catalina.loader.WebappClassLoaderBase loadClass
INFO: Illegal access: this web application instance has been stopped already.  Could not load org.apache.zookeeper.ClientCnxnSocketNIO.  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.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1777)
        at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1735)
        at ch.qos.logback.classic.spi.PackagingDataCalculator.loadClass(PackagingDataCalculator.java:199)
        at ch.qos.logback.classic.spi.PackagingDataCalculator.bestEffortLoadClass(PackagingDataCalculator.java:224)
        at ch.qos.logback.classic.spi.PackagingDataCalculator.computeBySTEP(PackagingDataCalculator.java:133)
        at ch.qos.logback.classic.spi.PackagingDataCalculator.populateUncommonFrames(PackagingDataCalculator.java:108)
        at ch.qos.logback.classic.spi.PackagingDataCalculator.populateFrames(PackagingDataCalculator.java:100)
        at ch.qos.logback.classic.spi.PackagingDataCalculator.calculate(PackagingDataCalculator.java:58)
        at ch.qos.logback.classic.spi.ThrowableProxy.calculatePackagingData(ThrowableProxy.java:100)
        at ch.qos.logback.classic.spi.LoggingEvent.<init>(LoggingEvent.java:128)
        at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:468)
        at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:424)
        at ch.qos.logback.classic.Logger.warn(Logger.java:753)
        at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1168)

 

2、解决方式

 

使用kill命令关闭tomcat进程

1、查看tomcat进程： ps -ef| grep tomcat

2、杀死tomcat进程： kill -9 xxx


3、再次重启tomcat，查看日志，不在报错。