Company an A project is released under the centos7 tomcat, there are other projects under the tomcat, publish A project encountered A strange problem,

1. The tomcat startup success, but not to A project, is A browser to access A project failure, and access to the tomcat log no refresh, other projects under the tomcat access is normal,
Closed this time of the tomcat, wait A few minutes after the restart tomcat, the project can be A normal visit (sometimes still cannot access, it is necessary to restart A few times more)

2. The tomcat release other projects, can also lead to A project appear afore-mentioned problems,

Every release A project, will clean up the work of tomcat folder, but still not solve,
Consult, which bosses encountered similar problems, or to know why and how to solve, please instruct me,

CodePudding user response:

Look the way you deploy,

If it is a war, it is need time self-extracting,

If not, check the error log at the bottom of the logs,

In addition Tomcat is configured to run depends on context, sometimes the Tomcat installation directory without any change, but the program can run, because changed the context. The XML, will work directory specified elsewhere,

CodePudding user response:

Occasionally meet, see log found is depend on the package haven't upload is complete, project has been loaded, prompt can not find rely on, loading failure,

Packaged as WAR upload can well solve this problem, a tomcat automatically after unpacking,

CodePudding user response:

Sorry, we are a tomcat release a project ~ ~ really want to get into a domain, also is nginx proxy

CodePudding user response:

For A project, is not each iteration will appear this problem, the iteration is relatively frequent, began to appear not to will be A little more, stop the tomcat, wait A few minutes after the restart, generally good, and occasionally)

Deployment is A war file to deploy, A project doesn't come, or any error in the log, and A new package project iteration, only the deployment package, did not change any configuration,

And the tomcat deployment of all projects under way are all the same, all operated by the script), currently only A project will appear sometimes cannot access problem,

CodePudding user response:

Look at the tomcat startup log

CodePudding user response:

How do I feel is your project itself has A problem? Have a screen

CodePudding user response:

I am the operations staff, issue to the developer, but because not every iteration of A project are A problem, operations will not prove to be A project their own problems,
So developers simply looked at it and reply no problem.