[tnist]

I have seen several post related to this topic but none with a good resolution.

My environment is as follows:

JBoss 3.2.5 / Tomcat 5.0.26
Eclipse 3.0
MyEclipse 3.8.1

Problem, when ever I attempt to redeploy a packaged archive, WAR file in this case, I get the following error:

Deployment is out of date due to changes in the underlying project
contents. You’ll need to manually ‘Redeploy’ the project to update
the deployed archive.

So I went an removed the .war file from jboss/server/default/deploy and cleaned up the work and tmp directories of JBoss. Then attempted to deploy the application but to no avail, same error message.

I am able to deploy it as and Expanded Archive.

So any ideas as to what is going on here and how do I correct it. I can always write my own ant script to build and deploy the archive, but that seems to be defeating the purpose of MyEclipse.

Thanks for the assistance in advance.

Regards,
Todd

[Riyad Kalla]

Todd,
Is JBoss running while you are trying to redeploy the WAR file? What happens when you stop JBoss and then click “Redeploy” does it work? When you try and “redeploy” and nothing seems to happen, is there an error displayed below in the textbox at the bottom of the deployment dialog if you select your JBoss deployment? Something about “failed”? When you click “redeploy” does a popup box quickly appear and then immediately disappear?

This kind of behavior is caused by the deployment failing to erase the existing WAR file due to a read-lock that the server has on the file, which makes it a PIA to deploy packaged WAR files on Windows to a running app server. Tomcat 5.5 has made provisions to avoid read-locks for this reason (you can see it at the bottom of the Tomcat 5.5 release notes) and on Unix/Linux you don’t run across this problem because of how the file systems are typically implemented.

[omulmann]

Hi,

I do not believe it has something to do with a read-lock, as this problem remain even after a reboot and under a new directory.
I guess there is a problem in your plug-ins (got this issue with Eclipse3 – myEclipse 3.8.1 and 3.8.0R2).
I have to come back now to Eclipse 2.1.3 and myEclipse 2.6.4).

A lot of time waste myking me re-thinking the added value of myEclipse.

Note:
I read few post where you are arguing that this issue has been fixed in your internal release.
But you know, when we come in such forum, it’s not to learn that if few week you will deliver a “working release”,
but to get an immediate solution. So if you have fix something, please allows peoples to download the delta.

Regards,
O. Mulmann

[Riyad Kalla]

O.,

I do not believe it has something to do with a read-lock, as this problem remain even after a reboot and under a new directory.

Are there any error messages in your log file? The problem the user posted above could possibly be completely different from your problem, I don’t think anyone is in a position (with the little information you have given) to say what is and what isn’t the problem. We need to analyze what is going on and fix it, simply posting “nope it doesn’t work and your product is buggy” doesn’t help anybody.

I guess there is a problem in your plug-ins (got this issue with Eclipse3 – myEclipse 3.8.1 and 3.8.0R2).

And if there is, we want to fix it. We have had one confirmed bug with deployment in the last 3 releases that was related to an empty /lib directory, other than that 99.9% of failed deployments have always had to do with incorrect configs or trying to deploy to a running app server that has locked the file. If you have found a *new* bug we definately want to investigate it and would appreciate your help with that or atleast steps to reproduce it.

[omulmann]

Hi,

As I’m having the same problem as Todd, I have customize below his post:

I have seen several post related to this topic but none with a good resolution.

My environment is as follows:

WebLogic 6.1
Eclipse 3.0
MyEclipse 3.8.1

Problem, when ever I attempt to deploy OR redeploy a packaged archive, WAR file in this case, I get the following error:

Deployment is out of date due to changes in the underlying project
contents. You’ll need to manually ‘Redeploy’ the project to update
the deployed archive.

Prior getting this message, I just got an Error Window without any text content nor Button in it

So I went an removed the .war file from my application directory (/bea/wlserver6.1/config/TNPdomain/applications)
Then attempted to deploy the application but to no avail, same error message.

I am NOT able also to deploy it as and Expanded Archive.

So any ideas as to what is going on here and how do I correct it. I can always write my own ant script to build and deploy the archive, but that seems to be defeating the purpose of MyEclipse.

NOTE:
Which log should I look at ? If it’s the Eclipse log, it didn’t provide any clue about the problem above

Thanks for the assistance in advance.

Regards,
O. Mulmann

[Riyad Kalla]

O.,
The bug you described (the empty popup dialog with a single button on it) is the bug we had related to an empty /lib folder in your project. Is this the case? Is your WebRoot/WEB-INF/lib empty? We also fixed this bug I believe in one of our quick fixes, what is the Build ID of MyEclipse that you are running (Window > Preferences > MyEclipse)? Our newest downloads from the website of version 3.8.1 have all 3 quick fixes integrated into them now, or you can download/apply the quick fixes manually if you haven’t done so already.

And yes I was referring to the Eclipse log file, so there was nothing in that talked about a “LibDeployment” or something like that?

[omulmann]

Hi,

well, I appreciate your support.
I fixed the problem rebuilding the .metadata directory under the workspace.

My apologize having thinking that the error wasn’t belonging to me.

Regards,
O. Mulmann

[Riyad Kalla]

I’m am glad that it is working now, that is all that is important. Thank you for following up with us.

[omulmann]

Hi,

just to let you know that the following config run well:

WebLogic 6.1
Eclipse 31M1
MyEclipse 3.8.1
(eclipse: jsdk 1.4.1_05, project: jdk1.3.1)

Be aware that the following message:
Deployment is out of date due to changes in the underlying project
contents. You’ll need to manually ‘Redeploy’ the project to update
the deployed archive.

appear if a deploy is attempted straight after a build with no refresh.
So just refresh your project before any deployment attempt (refresh might be configured automatically) but I prefer do it by my own.

Regards,
O. Mulmann

[chen7855]

I would like someone provide urgent help on following problem which is mentioned in other threads, but I was not able to find solution to my problem from previous posts.

The problem is that after I added some jar files to /WEB-INF/lib/ directory, and “Refreshed” project, I was not able to deploy it as packaged archive to weblogic server 8.1 anymore. In fact, I tried to deploy to other web servers, none of them works. I have made sure that all files I saw from Eclipse workbench are in sync with those in actual file system, and .classpath file was updated correctly with new jars, I even tried to delete .myeclipse directory manually after seeing below error in .log, but nothing worked. When trying to deploy, I got an empty error box, and deployment status showing:”Deployment is out of date due to changes in the underlying project contents ….”. I was able to deploy as exploded archive. I believe the problem is project specific, but could not figure out a way to fix.

My configuration is:
Eclipse 3.0
MyEclipse 3.8.2 GA

See below for error in .log under .metadata.

!ENTRY com.genuitec.eclipse.ast.deploy.core 1 1 Oct 01, 2004 14:45:52.941
!MESSAGE Build Exception
!STACK 0
com.genuitec.eclipse.core.GenuitecCoreException: Unable to clean build area C:/Program Files/eclipse/workspace/XDocsWeb_test/.myeclipse
at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer.privExportWebProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer.exportWebProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeploymentPackager.exportWebProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.WebDeployment.deployAsPackageArchive(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.redeploy(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog.ą(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog.access$2(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog$5.handleEvent(Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2772)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2431)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:668)
at org.eclipse.jface.window.Window.open(Window.java:648)
at com.genuitec.eclipse.ast.deploy.core.ui.action.DeploymentMgmtActionDelegate.runWithEvent(Unknown Source)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:266)
at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:206)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:915)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:866)
at org.eclipse.jface.action.ActionContributionItem$8.handleEvent(ActionContributionItem.java:824)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2772)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2431)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1377)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:254)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:335)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:183)
at org.eclipse.core.launcher.Main.run(Main.java:644)
at org.eclipse.core.launcher.Main.main(Main.java:628)
Caused by: org.eclipse.core.runtime.CoreException: Unable to clean build area C:/Program Files/eclipse/workspace/XDocsWeb_test/.myeclipse
at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer$1.run(Unknown Source)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1673)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1693)

Thanks!
Hannah

[Riyad Kalla]

Hannah,
Please close all your editors, and restart Ecllipse. After restarting, try and clean/rebuild your project, then remove the deployment and re-add it. Did that fix it?

[chen7855]

Thanks, I tried but it did not fix the problem. I am still getting the same error. FYI, I am able to deploy other project as war, that’s why I believe this is project specific, but don’t know what else to be cleaned up.

[Riyad Kalla]

I’ve asked someone to look at this ASAP that might know, thank you.

[Scott Anderson]

Hannah,

The .myeclipse directory is a temporary build directory that is created in your project root. If it can’t be deleted, it’s likely something is locking it in place. First, can you be sure that neither you or a team member added the directory to your version control system. To delete the directory, exit Eclipse and delete it from the Windows Explorer. Then, restart Eclipse and refresh the project. That should resolve the issue and “unstick” the project.

[chen7855]

The problem seems to have disappeared after I removed 4 weblogic jar files (weblogic.jsr, etc.)from /WEB-INF/lib/ of the project. These 4 jars are among the jar files I added to the project’s /WEB-INF/lib/ before the problem started to occur. I could not really explain how they could cause the problem — I refreshed the project several times and stopped weblogic on my machine before running the deployment. Maybe you can explain the connection.
Thanks!

[Author]

Posts