I recently started getting an error when deploying to Tomcat 5.5 or when using a custom location. I get the error message:

Deployment failure on <Custom Location>. Could not copy all resources to C:\servers\Tomcat55\webapps\my-web-app. If a file is locked, you can wait until the lock times out to redeploy, or stop the server and redeploy, or manually remove the deployment at C:\servers\Tomcat55\webapps\my-web-app

This happens while Tomcat is not running and no other application is touching the directory. This also happens when I deploy to any other location (such as C:\temp\my-web-app) which leads me to believe that it is not because a file is locked by another application but possibly locked by Eclipse. This appears to cause my application to not be deployed completely.

I am having this problem with 5.5.0M2 but I also had the problem with 5.1.

I recently installed a new version of the Maven2 plugin and this may be related.

My Questions:
1. How can I find out what file is being locked or get this error to log?
2. Has anyone else seen this? Is this a known issue?
3. How can I work around it?

Thanks,
Kurt

My configuration:

*** Date:
Friday, April 13, 2007 11:43:31 AM CDT

** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_07


*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 5.5.0 Milestone 2
Build id: 20070409-5.5.0-Milestone2


*** Eclipse details:
Eclipse SDK

Version: 3.2.2
Build id: M20070212-1330




Eclipse Graphical Editing Framework

Version: 3.2.2.v20070208
Build id: 20070208-1315


Eclipse Platform

Version: 3.2.2.r322_v20070119-RQghndJN8IM0MsK
Build id: M20070212-1330


Eclipse Java Development Tools

Version: 3.2.2.r322_v20070104-R4CR0Znkvtfjv9-
Build id: M20060921-0945


Eclipse Graphical Editing Framework

Version: 3.2.2.v20070208
Build id: 20070208-1315


Eclipse Project SDK

Version: 3.2.2.r322_v20070104-dCGKm0Ln38lm-8s
Build id: M20070212-1330


Eclipse RCP

Version: 3.2.2.r322_v20070104-8pcviKVqd8J7C1U
Build id: M20060629-1905


Eclipse Plug-in Development Environment

Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG
Build id: M20060921-0945




Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\tools\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
9b4_a0
-clean
-vm
C:\tools\jdk1.5.0_07\bin\javaw.exe

Kurt,
First remove all your deployments and right-click Refresh all your projects. Then go to Project and clean-all your projects.

Then restart using the -clean command line argument and recreate your individual deployment. Is it working now?

I also have this problem, and my environment is similar to Kurts. I have Maven 2 plugin 0.0.10 installed, and I didn't have the problem with 0.0.9. I've tried to above procedure but no change, tha deploy still fails. When I look what has been deployed, all except the libs are there. It's probably a Maven 2 plugin issue, but maybe it isn't.

thanks,

Niklas

I too have this problem in MyEclipse 5.5.1 (all-in-one install). I can run from the command line fine. Here is what I get in the console if it helps:

Code:

[INFO] Scanning for projects... [INFO] ---------------------------------------------------------------------------- [INFO] Building batch-capture [INFO]    task-segment: [test] [INFO] ---------------------------------------------------------------------------- [ERROR] project-execute : crown:batch-capture:jar:0.3.0 (  task-segment: [test] ) Diagnosis: Error configuring: org.apache.maven.plugins:maven-clean-plugin. Reason: Unable to parse the created DOM for plugin configuration FATAL ERROR: Error executing Maven for a project [ERROR] reactor-execute : C:\Java\work\trunk\batch-capture Diagnosis: Error configuring: org.apache.maven.plugins:maven-clean-plugin. Reason: Unable to parse the created DOM for plugin configuration FATAL ERROR: Error executing Maven for a project [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-clean-plugin:2.1.1 Cause: Error loading class 'org.apache.maven.plugin.clean.Fileset' [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1 second [INFO] Finished at: Fri May 25 10:59:09 EDT 2007 [INFO] Final Memory: 2M/4M [INFO] ------------------------------------------------------------------------ [INFO] Error for project: batch-capture (during test) [INFO] ------------------------------------------------------------------------ [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-clean-plugin:2.1.1 Cause: Error loading class 'org.apache.maven.plugin.clean.Fileset' [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [ERROR] reactor-execute : C:\Java\work\trunk\batch-capture FATAL ERROR: Error executing Maven for a project [INFO] BUILD ERRORS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1 second [INFO] Finished at: Fri May 25 10:59:09 EDT 2007 [INFO] Final Memory: 2M/4M [INFO] ------------------------------------------------------------------------

Guys there seems to be some bug with the new Maven2 plugin that is pissing off the MyEclipse deployment tool. I had a user email us and another post in the forums about it (deployments totally barf with all sorts of directory errors and what not when Maven2 is enabled).

For the time being can you guys step back to Maven .9 plugin to get it atleast working? Also did anyone file it with the Maven team or see if it's already filed?

It's filed under http://jira.codehaus.org/browse/MNGECLIPSE-323 with no comments from the Maven team yet.

Thank you for the link (for tracking)

I have the same question. But I did not have a Maven plug-in installed. I'm using MyEclipse 5.1.1 GA.

archerzz wrote:

I have the same question. But I did not have a Maven plug-in installed. I'm using MyEclipse 5.1.1 GA.

The error has been resolved. It's caused by the errors in the project. MyEclipse will prevent some resources with errors to be deployed. That's why some files are locked.
I think the error message is not user-friendly.

Hi Friend I am new with MyEcllipse 5.5.1 GA , Iam trying to developing a web application using tomcat 5 , but when i am trying to confuigure tomcat 5 with myProject
it shows message that the , application sever noty confuigure properlly ,
can anybody , give me step by step solution
thanks

Make sure you have your Tomcat connector configured correctly. This is what it should look like.
http://www.myeclipseide.com/PNphpBB2-viewtopic-t-13941-sid-24d2a7a4572edb755ac9b62ac1e97523.html

jitu_ragse,
If the error is pertaining to "JDK", you need to go to the JDK sub-preference-panel under the Tomcat 5 connector, and click "add" and configure it to run with a JDK, not the default JRE that it picks up. Sorry about the trouble.

We're having the exact same error as in the opening post here.

Quote:

Deployment failure on Tomcat 5. Could not copy all resources to /home/arjan/apache-tomcat-5.5.20/webapps/Root. If a file is locked, you can wait until the lock times out to redeploy, or stop the server and redeploy, or manually remove the deployment at /home/arjan/apache-tomcat-5.5.20/webapps/Root.

We're not having any maven plugin installed (just bare Eclipse 3.2.2/MyEclipse 5.1.1) and Tomcat is surely not running. I tried deleting manually, checked all file permissions, created a new workspace, new svn checkout and a whole new Tomcat installation, but the problem persists.

I did notice the problem is related to a single specific project. Other projects in my workspace deploy just fine. Appearently, in that project there is some faulty file that MyEclipse can't or won't deploy.

The problem is that MyEclipse only tells me it could not copy "all" resources. It gives no clue about which resource is problematic, so I have no idea where to start looking right now.

I'm working on Debian Etch btw, using a SUN 6.0U1 JDK. I also tried on a Debian Lenny machine, but the results were the same.

To follow up on this. By tracking back in our SVN to revisions of the mentioned project that did work, I was able to find the file that caused all these problems: .classpath. Apparently someone had added a non-existing .jar file entry to it.

Still I think it would be a lot more helpfull if MyEclipse had told me why it could not deploy. Would have saved me quite some time...

Arjan that's really frustrating. We agree that it should report where it got hung up, I've filed an enhancement request to the deployment module. Sorry for the headache.