[Hellmut Adolphs]

Hi, our development team has been a bunch of happy users of myeclipse for quite a while. We develop major applications.. and we are always testing with the latest betas an releases. Some of us have contributed to bugs reports as well. Now, we are having the following problem, as always I Hope you guys can help us out:

It started to happen with those people who updated to beta-2 from scratch (in a fresh eclipse install), but now.. all those of use who updated with the udpating site are also having the problem.

Each time we try to re-deploy an EAR or deploy for the first time or remove/deploy (we have tried all the cases) we get a report that we had never seen before:

1. When we click FINISH in the deployment window it starts deploying, but at a certain point an error window pops-up with NO message, EMPTY.. it just says error in the top of the window.
2. We click OK.. and then it returns to the project deployments window, there we see a new message with the warning icon: “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.”
3. We have tryied hitting ‘redeploy’ many times and each time the EAR is geneareted differently, with different missing files or jars… its very weird, then when we run Jboss it obviously pops up a bunch of deployment errors and missing classes messages.

All of our machines are using ECLIPSE 3.0 Final release
I have checked the PDE Error log in eclipse and found a series of errors common in all of the machines:

1. The first error in the list is a “Unhandled event loop exception”
With no exception stack trace found for it. Plus no session data.
2. The second error in the list is a java.lang.NullPointerException with the following stack:
java.lang.NullPointerException
at com.genuitec.eclipse.ast.deploy.core.DeploymentUtil.getWebLibJarNames(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeploymentUtil.deployExternalLibraries(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.WebDeployment.Ă(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.WebDeployment.resyncAll(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ModuleDeployment.deployAsExplodedArchive(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.EARDeployment.resyncAll(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.EARDeployment.deployAsExplodedArchive(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:954)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2595)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2298)
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.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:915)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:866)
at org.eclipse.jface.action.ActionContributionItem$7.handleEvent(ActionContributionItem.java:785)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:954)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2595)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2298)
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)

So far I Have 5 developers with the same problem all with same configuration:

– All of us running Linux either SUSE 9.1 or Red hat 9
– Eclipse Platform Version: 3.0.0 Build id: 200406251208
– Some of us have additional plug-ins like: Subclipse and mavenIDE but some of us have fresh installs with the same error and only MyEclipse as external plug-in.
– My plugins directory shows 8 plugins with the packaging
org.eclipse.pde.*
– We are all using: MyEclipse Version: 3.7.200
Build id: 200407091200-3.8-Beta2
-Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
– The error log in the .metadata directory of the workspace reports those 2 same exceptions I mentioned above.

Thanks for any help with this issue 🙂

– Hellmut

[Riyad Kalla]

Hellmut,
This is the exact behavior we are seeing with a bug we are currently working on where the EAP project contains a web application that does not contain any JAR files in its WEB-INF/lib folder. Do any of your modules in the EAP project contain such a web module project?

[Hellmut Adolphs]

Ok.. another udpate
We have found several weird behavior on the tool now:

1. When we remove a module from the EAR it is not removing it from the application.xml file.
2. When we add a module to the EAR it adds it again and then we have 2 entries repeated… obviously generating an error.
3. When I removed an EJB module from the EAR,somehow it removed the reference in the web.xml projects and in the classpath file from the Web module associated in the EAR project…
All this bogus beahavior I Haven’t seen before. Now, every time I deploy /redeploy I get different results, some times it adds one of the EJB modules and the web module, some times just the web module.. but not all of the modules… I always get those errors an messages I Reported above.

please help!

Thanks,

-Hellmut

[Scott Anderson]

Hellmut,

1. When we remove a module from the EAR it is not removing it from the application.xml file.

I tried to replicate this with several different variations on Eclipse 3.8Beta-2 and Eclipse 3.0 but could not. What version control software are you using? Is application.xml writable? Do you have auto build turned on in the workspace? Are you talking about the application.xml file in the workspace, the deployed one, or both? Are you using packaged or exploded deployment?

All this bogus beahavior I Haven’t seen before.

Neither have I, and I don’t seem to be able to replicate it.

2. The second error in the list is a java.lang.NullPointerException with the following stack:
java.lang.NullPointerException
at com.genuitec.eclipse.ast.deploy.core.DeploymentUtil.getWebLibJarNames(Unknown Source)

However, as Riyad pointed out there is a know bug if you have a web project that doesn’t contain a WEB-INF/lib directory. If that’s the case, the workaround is simply to create an empty WEB-INF/lib directory prior to deployment. That’s what is causing the exception you’re seeing in the log file. We’ll get that fixed for 3.8 GA, but this might be messing up all the deployments and edits.

For any installs you did from the update site, please be sure to update them as specified in this thread:
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-2916.html

[Hellmut Adolphs]

scott,

Sorry for the delay I was having lunch 😆

Ok, here are some answers.. but first the most important information is, yes we do have a web module with an empty WEB-INF/lib folder, I will try that work around you guys mentioned and post my results. thanks a lot for that prompt reply ! 🙂

I tried to replicate this with several different variations on Eclipse 3.8Beta-2 and Eclipse 3.0 but could not. What version control software are you using? Is application.xml writable? Do you have auto build turned on in the workspace? Are you talking about the application.xml file in the workspace, the deployed one, or both? Are you using packaged or exploded deployment?

We are using for this particular application CVS 1.11, yes we have auto-build feature turned on in the workspace. And I was talking about the application.xml file in the EAR project but in the workspace… it obviously genereated an error on build so I Have to manually remove the repeated modules. And, we are using exploded deployment.

For any installs you did from the update site, please be sure to update them as specified in this thread:
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-2916.html

Thanks! Correct me if I am wrong, but does this fix only apply to people who were using an outdated version of GEF? I didn’t seem to be having any issues with the UI but.. I did notice some weird errors reported by the core ui classes of Eclipse, so I will patch it and run the patch on all our dev machines.. at least on those who were updated from the update site.

Again, Thanks a lot guys, I will post my results in a bit. 🙂

-Hellmut

[Hellmut Adolphs]

Hey there,

OK, the work around works as you said and we are able to deploy again. thanks!

BUT: That bug I Mentioned is still there (the application.xml file not being udpated)
This is the way to replicate it:

1. Right click on the EAR project –> my eclipse –> Add and Remove modules
2. Select a module (I.e. an ejb module) click Remove. DO NOT CLICK OK YET
3. Click Add now, re-Add the same module again. NOW click OK
4. You will see inmediatly the error on application.xml becuase the module is still there

This is a very simple bug, its just that the file is not being updated until your press OK, so when you remove and add the same module in the same window then you have the module repeated in the application.xml file.

Hope this helps tracking it down, thanks guys for your help! keep up the great work! 🙂

later,

-Hellmut

[Hellmut Adolphs]

Another question:

Checking that application.xml bug, I remember about a particular behavior I Noticed, here is the question:

– We added to other modules to the Application.xml file in the EAR project that are NOT eclipse projects, they just are jars in the lib directory of the EAR Project. LIke this:

<application>
<display-name>XXXEAR</display-name>
<module id=”myeclipse.1084974569902″>
<web>
<web-uri>XXXWeb.war</web-uri>
<context-root>/</context-root>
</web>
</module>
<module id=”myeclipse.XXXMainEJB”>
<ejb>XXXMainEJB.jar</ejb>
</module>
<module id=”myeclipse.CEAEntityEJB”>
<ejb>XXXEntityEJB.jar</ejb>
</module>
<module id=”XXX-cluster”>
<ejb>lib/XXX-cluster.jar</ejb>
</module>
<module id=”XXX-queue”>
<ejb>lib/XXX-queue.jar</ejb>
</module>
</application>

Well, what happens is, when we add or remove a module in the EAR Project , those modules that are not projects in the workspace, dissapear. Is this normal? I Mean is this the expected behavior? what we do each time is just … re-input by hand in the xml file… so we can test in our local envronments… since our real deploy is all handled by ant.

Thanks! 🙂

-hellmut

[Riyad Kalla]

Ahhh ok yes we got it! Thanks for the step-by-step, I’ll file this right now.

[Scott Anderson]

Hellmut,

OK, the work around works as you said and we are able to deploy again. thanks!

That’s great news. Sorry about the bug, but the workaround is only temporary. We’ll definately get it fixed for 3.8 GA.

BUT: That bug I Mentioned is still there (the application.xml file not being udpated)
This is the way to replicate it:
<steps elided>

Ah! Now I can reproduce it. It never dawned on me to remove and add the same module, thus doing nothing, then hitting OK. I’ll be sure a bug report gets filed so we can take care of it. Of course the workaround is: if you really don’t want to do anything, don’t select ‘Add and Remove modules’. 😉

[Hellmut Adolphs]

Another interesting observation:

– I noticed that the Add/remove modules feature of my eclipse (I don’t know if this was related to the lib/jar file or is also affected by doing add/remove in the same window) modified also my .mymetadata and .project files.
– .mymetadata: That module I Played with to remove/add in the same window (the one that affected application.xml) also was entered repeated in this file. So, in other words, what happened with application.xml file also happened with .mymetadata file.
– .project: The remaining projects after an add/remove on the EAR Project were actually added as referenced projects in the module, like this:
<projects>
<project>XXXWeb</project>
<project>XXXMainEJB</project>
</projects>

Hope this info also helps.

Thanks,

-Hellmut

[Scott Anderson]

Hellmut,

The modification of .mymetadata is expected and I noted it in the bug report. Application.xml is actually generated from the metadata file so we’d have an even bigger issue if one changed and the other didn’t. Thanks for taking the time to document this so we can address it.

[Hellmut Adolphs]

Scott,

No problem, glad I could help some how. Thanks! 🙂

-Hellmut

[Author]

Posts