-
-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
集成后,不定时在tomcat里报错 #644
Comments
几个应用放到一个tomcat里运行的。这几个应用都集成Apollo了。 |
这个是tomcat shutdown阶段的一个thread check,Apollo的线程都是daemon线程,所以没关系的。 至于那个报错是因为在shutdown阶段,线程执行的时候,一些class已经unload掉了,所以也是正常的。 |
先关闭了。 |
请问你最后怎么解决的?我现在也遇到这个问题了 |
同上 |
怎么解决了,我至今也没解决 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
你好!集成apollo后,发现在tomcat里运行时,不定时的会报这个错误。现象是看到有tomcat进程,但是访问端口已经是404了。这是最后出现的日志。有什么建议吗?
Jun 19, 2017 3:36:28 PM org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already. Could not load com.ctrip.framework.apollo.Apollo. 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:1599)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1558)
at com.ctrip.framework.apollo.internals.RemoteConfigRepository$1.run(RemoteConfigRepository.java:114)
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)
The text was updated successfully, but these errors were encountered: