Tomcat Manager 404 application after changing Context.xml

Question

I have Tomcat 7.0.39 installed on CentOS 6.6 x64

I configured it correctly to go into the Tomcat manager application. Then I changed /conf/context.xml to another context.xml file (for the client application I was trying to run). After changing the context.xml file, I got 404 when navigating to the manager application.

The problem is that after changing context.xml back to the source context.xml file, I still get 404 when navigating to the manager application (although the only thing that has been changed is the context.xml file and this file is back to the original state).

I tried the following to start the manager application again:

• Restarting tomcat service (multiple times)
• Rebooting the entire virtual machine
• Removed everything in / work / Catalina /
• Remote manager from / webapps and then added it back when tomcat was started (Tomcat admitted that he had a new webapp and then started to deploy it)

There are no errors in the logs, and catalina.out shows that the manager application is deployed when tomcat starts:

INFO: Deploying web application directory /usr/share/apache-tomcat-7.0.39/webapps/manager 

My question is, what part of tomcat stores this broken state? I would think that, returning to the original, the working .xml context will make my tomcat work again, so what can this tomcat file change that persists even after restarting tomcat?

Answer 1

How much important information is missing, I can also assume.

• You may have confused files with the permissions /conf/context.xml and Tomcat can no longer read the file.
• You may have incorrectly restored the old file (it may be corrupted).
• You may have changed something else that was important, but forgot about it.
• You may be calling the wrong URL. It should be like http: // localhost: 8080 / manager / html