Modify the JSP file Tomcat publishing failed (Could not delete could locked by another process)

When the project modifies the JSP file, Tomcat cannot publish it,

Publishing failed with multiple errors
Could not delete D:/tomcat 6.0/webapps/server/web-inf/platform/configuration/org.eclipse.core.runtime/.manager/. Tmp1900396474661591532.instance. C.
Could not delete D:/tomcat 6.0/webapps/server/web-inf/platform/configuration/org.eclipse.core.runtime/.manager/. Tmp1907896664996379798.instance. May is locked by another process.
Could not delete D:/tomcat 6.0/webapps/server/web-inf/platform/configuration/org.eclipse.equinox.app/.manager/. Tmp2761653564891974481.instance. May is locked by another process.

Two solutions were found on the Web 1. Modify the project's publishing address: Original: I was getting the annoying error in Eclipse with Tomcat where it didn ' t think it could publish an Application since some files were locked, when they were locked by the Javaw.exe process that Eclipse.exe started. The fix for me is to not having "use Tomcat Installation" selected in my server configuration. When I switched back to the default of "Use Workspace metadata", the error stopped happening. [http://byprogrammerforprogrammer.com/2009/12/ Eclipsetomcat-publishing-lockup-could-not-delete-file-may-be-locked-by-another-process/]2.clean
Original: I performed a "clean" operation on the Tomcat server instance and the problem just went away. It ' s being doing fine since that. I ' ll let you know if I see this issue again. [Http://forums.adobe.com/message/2457298?tstart=0] (3/F:) When I used this method, the problem was just beginning to disappear, but after a while it was old again. It occurred to me that there was no problem with other projects under the same eclipse, there could be a problem with the project setup, the Web project referencing another Java project (Project B), two projects having the same jar package, is not the issue of these same jar releases, I removed the jar package reference in Project B's Java EE module Dependencies (Project B right-->properties->java EE module Dependencies) and solved the problem.

3.new Server

A simple and effective way to delete the original Tomcat server, and then re-new one!!! Don't get tangled up. Gaga: P

Re-establish a server, and then switched back to the default of "Use workspace metadata", problem solving, OH yeah!!!

Modify the JSP file Tomcat publishing failed (Could not delete could locked by another process)