Tomcat Start 报错 (COULD NOT DELETE MAY BE LOCKED BY ANOTHER PROCESS)

jsp文件重命名后发布不起来了,提示文件被占用,原因是当前的java ee项目 与它引用的java项目 依赖了相同的jar包,删除了clean 再发布,问题解决,如有需要再引用回来

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

环境:eclipse tomcat 之前使用没有什么问题但是突然项目修改jsp文件后,tomcat不能发布, 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 be 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 be locked by another process.   网上找了两种解决办法 1.原文: 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 was to not have “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.原文  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楼: )    
     我使用这种方法时,问题刚开始消失了,但过了一阵又是老样子。   我突然想到同一个eclipse下的别的项目使用的时候没有出现这个问题,有可能是项目设置的问题, 这个web项目引用了另外一个java项目(项目B),两个项目有一些相同的jar包,是不是这些相同的jar发布的问题呢,我把项目B的 Java EE Module Dependencies(项目B右键->Properties->Java EE Module Dependencies)里的jar包引用去掉,问题解决了。

时间: 2024-08-07 17:39:11

Tomcat Start 报错 (COULD NOT DELETE MAY BE LOCKED BY ANOTHER PROCESS)的相关文章

修改jsp文件tomcat发布失败(Could not delete May be locked by another process)

突然项目修改jsp文件后,tomcat不能发布, 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

Tomcat启动报错[org.apache.struts2.dispatcher.Dispatcher]Dispatcher initialization failed

Tomcat启动报错: [org.apache.struts2.dispatcher.Dispatcher]Dispatcher initialization failed Unable to load configuration. - bean - jar:file:/E:/SoftwareDevelopment/Software/Eclipse4.3/eclipse-jee-kepler-SR1-win32-x86_64/Workspace/.metadata/.plugins/org.ec

启动Tomcat服务器报错

启动Tomcat服务器报错: Several ports (8005, 8080, 8009) required by Tomcat v5.5 Server at localhost are already in use. The server may already be running in another process, or a system process may be using the port. To start this server you will need to sto

Android 启动Tomcat服务报错,端口占用解决方案

启动Tomcat服务器报错:Several ports (8005, 8080, 8009) required by Tomcat v5.5 Server at localhost are already in use. The server may already be running in another process, or a system process may be using the port. To start this server you will need to stop

Tomcat启动报错java.net.AbstractPlainSocketImpl(java/net/AbstractPlainSocketImpl.java:178:-1)Struts在网络复杂情况下启动报错解决办法

SSH项目 在网络复杂的情况(具体规律未知)下,Tomcat启动时,报如下错误: [ERROR] 2014-08-12 14:52:58,484 [org.apache.struts2.dispatcher.Dispatcher :27] - Dispatcher initialization failedUnable to load configuration. - Class: java.net.AbstractPlainSocketImplFile: AbstractPlainSocket

Tomcat启动报错:严重: StandardServer.await: create[8005] java.net.BindException: Cannot assign requested address

org.apache.catalina.core.StandardServer await        SEVERE: StandardServer.await: create[8005]:        java.net.BindException: Cannot assign requested address java.net.BindException: Cannot assign requested address        at java.net.PlainSocketImpl

<<< Tomcat运行报错IOException while loading persisted sessions: java.io.EOFException

解决方法:将work下面的文件清空,主要是*.ser文件,或者只是删除掉session.ser即可以解决. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

tomcat启动报错,找不到相应的 queue,从而引发内存泄漏

tomcat启动报错,无法创建 bean listenerStatusChangeDealHandler, no queue 'STOCK.NOTIFY_CHANGE.INTER.CACHE.QUEUE' in vhost 从启动日志来看,有时候仅会看到内存泄漏,而没有与queue相关的日志,非常easy走错方向. 依照 http://blog.csdn.net/wangjunjun2008/article/details/23375501 的方法能够看到具体日志,从而确定报错原因 tomcat

Tomcat启动报错org.springframework.web.context.ContextLoaderListener类配置错误——SHH框架

SHH框架工程,Tomcat启动报错org.springframework.web.context.ContextLoaderListener类配置错误 1.查看配置文件web.xml中是否配置.org.springframework.web.context.ContextLoaderListener在web.xml配置文件中已经配置 2.查看工程是否添加此jar包,org.springframework.web.context.ContextLoaderListener的jar包为spring

tomcat启动报错,找不到对应的 queue,从而引发内存泄漏

tomcat启动报错,无法创建 bean listenerStatusChangeDealHandler, no queue 'STOCK.NOTIFY_CHANGE.INTER.CACHE.QUEUE' in vhost 从启动日志来看,有时候仅会看到内存泄漏,而没有与queue相关的日志,很容易走错方向. 按照 http://blog.csdn.net/wangjunjun2008/article/details/23375501 的方法可以看到详细日志,从而确定报错原因 tomcat启动报