[mst98sub]

Hello Support,

at the moment we are testing MEB with WebSphere AS.
Mostly the deployment of our test application works fine.
But in 10 to 20 percent the deployment fails with the following error messages:

[11.11.08 18:31:43:315 CET] 00000047 AddBinaryTask E EAR expansion failued for C:\Programme\IBM\WebSphere\AppServer0\profiles\AppSrv01\installedApps\myhostNode01Cell\XYZ.ear

Followed by the following error:

[11.11.08 18:31:44:705 CET] 00000049 ApplicationMg W WSVR0100W: Beim Initialisieren von XYZ ist ein Fehler aufgetreten.
com.ibm.ws.exception.ConfigurationWarning: Module not found

Thereafter MyEclipse mostly shows no error message box.
The partially deployed application is listed in the servers tab,
but marked with a yellow exclamation mark.

In some rare cases you can undeploy the application and just try it again.
But most of the time, the undeployment or at least the new deployment fail.
Stopping the server sometimes helps.
But mostly that doesn’t help either, and MyEclipse is not able to undeploy and deploy the application, even with a stopped server.
Then you have to restart eclipse.

As described in the following threads on IBM forums,
there was a bug in WAS 6.0, but we are using WAS 6.1.0.17:
http://www-128.ibm.com/developerworks/forums/thread.jspa?threadID=146246
http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14127394
So I’m not sure, whether it’s a WAS or a MEB bug.
Could you please help me to fix the problem?

Probably it is important to note, that this error never occured, when I exported the EAR from MEB and installed it using the WebSphere Admin Console.
Furthermore the error also never occured, when I built and deployed the same project running my handwritten maven2 pom files from a command line.

thx,
Mathias

WebSphere Version 6.1.0.17 + EJB 3.0 FP
MyEclipse 7.0M2 (and Version 6.5.1)

[Riyad Kalla]

Mathias,

To help us narrow down what is going on here, if you shut down the server and try and deploy/redeploy a few times, is the deployment fine? Does this only occur when the server is started and on the 3rd or 4th attempt at a redeploy the deployment will break?

We’ve seen this once before but it’s hard to reproduce issues like these without the specific projects that can cause problems, so let’s dig out identifiable bits of information and see what we can find.

[mst98sub]

The problem still exists in MyEclipse Blue Edition 7.0.
So perhaps we can find some work around, now.

Currently my problem is, that MyEclipse suddently can’t do an “exploded deployment” anymore. Then the error message is “Exploded location overlaps an existing deployment”.

While the server was running, I’ve successfully deployed und undeployed my ear several times. But suddenly a deployment attempt fails with the message mentioned above.

To answer your question: The problem never occured while deploying to a shut down server. But once the problem occured, a server shut down does not change the situation. Only restarting MyEclipse helps.

Steps to reproduce:
1. Start MyEclipse
2. Start WebSphere 6.1
3. Deploy and undeploy an EAR as “exploded archive” server times
4. Deployment suddenly and for all later attempts fails with “Exploded location overlaps an existing deploy”
5. Stop WebSphere 6.1
6. Deployment still fails with “Exploded location overlaps an existing deploy”
7. Restart MyEclipse
8. Start WebSphere 6.1
9. Exploded deployment works fine again

How does MyEclipse check that there is an overlapping exploded deployment?
Can I some how refresh this state without restarting MyEclipse?
Or can I prevent MyEclipse from getting into this state?

[Greg]

Try closing and reopening the project. If that doesn’t work, you can close the project, remove your server configuration (“restore defaults”) and then readd server config and then reopen your project. Sorry for the inconvenience.

[Author]

Posts