Tomcat Start Error (COULD not DELETE could LOCKED by another PROCESS)

JSP file is not published after renaming, prompting the file is occupied, because the current Java EE Project and its reference to the Java project relies on the same jar package, removed the clean re-release, problem solving, if necessary to re-reference back

http://it.zhaozhao.info/archives/44926

Environment: Eclipse Tomcat is not a problem to use before, but suddenly after the project modifies the JSP file, Tomcat cannot publish, 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. Original: I was getting the annoying error in Eclipse with Tomcat where it didn ' t think it could publish an Applica tion 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/]

Modify the publication address of a project
But it didn't work on my machine, and I found another way. 2. Original text I performed a "clean" operation on the Tomcat server instance and the problem just wen T 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 floor:)
When I used this method, the problem was just beginning to disappear, but after a while it was old. 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.

Tomcat Start Error (COULD not DELETE could LOCKED by another PROCESS)