1, see: This Web application instance have been stopped already
Therefore, it is possible to send a reboot if Tomcat is required, which is the first condition of error.
2, see: Could not load ...
Look at this can't directly introduce the problem to produce conditions, but it is obviously about loading.
Summing up the above two points, popular point, is to restart the project (perhaps because of the direct modification of code, engineering reload), and, even after the database (login, etc.), the above error message appears.
Here is the Tomcat Server.xml configuration:
<context debug= "0" docbase= "E:\Workspaces\CTC-ERP_KF\web" path= "" reloadable= "false">
</Context>
The reason for this is that Tomcat reloads the Web application as a result of the failure. When an application unloads, it does not close all threads. When Tomcat has closed its classloader, some threads continue to run, causing an error. But this does not affect the normal use.
Context (Represents a Web application, usually a war file, see the servlet specification for specific information about the war) |
DocBase |
The path to the application or the path where the war file is stored |
Path |
Represents the prefix of the URL for this Web application, so the requested URL is http://localhost:8080/path/**** |
Reloadable |
This property is important, and if true, Tomcat will automatically detect changes in the application's/web-inf/lib and/web-inf/classes directories, automatically load new applications, and we can change the application without restarting Tomcat (hot deployment) |
Tomcat_this Web application instance has been stopped already