Tag Archives: Removing obsolete files from server… Could not clean server…

After modifying Tomcat’s server.xml, the Tomcat deployment project reported an error: removing observe files from server… Could not clean server

This article gives you a comprehensive understanding of Java object serialization and deserialization>>>

The second is that when you are in clean tomcat, the file is not clean. (temporary crash, system downtime or other reasons)
causes that the service.xml in eclipse is not consistent with the copy when you are cleaning.

solution:

1 find your tomcat folder. Find the service.xml file in it (path tomcat, conf, service. XML)

2,
Find service.xml in workspace \. Metadata \. Plugins/org. Eclipse. WST. Server. Core/tmpx (x is 1… N, depending on your project) conf
to see if this file is the same as your service.xml file.

if not, replace the temporary file in eclipse 2 with your service.xml.

the two files should be consistent before you can start Tomcat


[Ultimate Solution:]
1. Clean up all your Tomcat configurations
2. Clean up all the files in the workspace. Metadata. Plugins \ \ org. Eclipse. WST. Server. Core directory
3. Download the new Tomcat example:http :// archive.apache.org/dist/tomcat/tomcat-7/v7.0.77/bin/apache-tomcat-7.0.77. Zip
4. Restart your eclipse.
5. Reconfigure ecipse’s Tomcat (newly downloaded)

*********************************************************************************************
eclipse:Cannot Perform O peration:The resource Is not on the build path of a java project
modify the. Project file at the root of the workspace, After adding the following contents, restart Eclipse:

<natures>
   <nature>org.eclipse.jdt.core.javanature</nature> <nature>org.eclipse.m2e.core.maven2Nature</nature> </natures>


In the face of such a problem, my first approach is to delete Tomcat and rebuild a server. However, the server.xml in Tomcat has to be reconfigured again, which is not cost-effective. I have been on the Internet for a long time, vaguely using the methods provided by netizens and my own attempts, and found a feasible method. I hope it will help you

Make sure that the server.xml of Tomcat in eclipse is consistent with the conf/server.xml in the root directory of tomcat, and then delete all problems in the temp0 folder of. Metadata. Plugins \ \ org.eclipse.wst.server.core in the workspace working directory of eclipse, and then rerun the project to start the server normally,

Original text: https://blog.csdn.net/hd20086996/article/details/51683813