- This topic has 5 replies, 2 voices, and was last updated 12 years, 1 month ago by support-pradeep.
-
AuthorPosts
-
viswamy2kParticipantHi,
We are experiancing a error while deploying to JEE6 EAR with EJB2.1 module,What we came to know is that MyEclispeBlue 10.6 is validating for casesesitivity against the JAR name for any module added to EAR, follwoing is the stack trace
org.eclipse.core.commands.ExecutionException: Colliding case insensitive project names …….
at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.importEar(BatchExtension.java:1131)
at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.runEarDeploy(BatchExtension.java:379)
at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.run(BatchExtension.java:356)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1957)
at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.execute(BatchExtension.java:321)
at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.run(BatchExtension.java:284)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:613)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:613)
at com.ibm.etools.ejbdeploy.batch.impl.BootLoaderLoader.run(BootLoaderLoader.java:494)
at com.ibm.etools.ejbdeploy.batch.impl.BatchDeploy.execute(BatchDeploy.java:114)
at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:106)
at com.ibm.etools.ejbdeploy.EJBDeploy.deploy(EJBDeploy.java:348)
at com.ibm.etools.ejbdeploy.EJBDeploy.main(EJBDeploy.java:309)Could you plese let us know how to solve this problem
thanks in advance
-viswa
support-pradeepMemberviswamy2k,
Sorry that you are seeing this issue.
1) Can you please list out the exact steps in detail right from the EAR and EJB creation to deployment to help us replicate the issue at our end ?
2) Which application server are you working with ?
3) If possible, can you please prepare a sample project which exhibits the issue and send it to us to help us investigate further?
viswamy2kParticipantHi,,
1) Can you please list out the exact steps in detail right from the EAR and EJB creation to deployment to help us replicate the issue at our end ?Here are the steps :
a. We have upgraded the EAR to JEE6 level
b. Added the EJB2.1 to the JEE6 EAR
c. Then deploying this EAR to WAS8.5 on MyEclipseBlue 10.6 (This time we are getting the mentioned error)
d. The problem what we observed is if the EJB jar(which is part of EAR lib) name doesnt match with the EJB project name in terms of casesensitivity the prolem is occuring2) Which application server are you working with ?
a. WAS8.5 (we moved fom WAS7015)3) If possible, can you please prepare a sample project which exhibits the issue and send it to us to help us investigate further?
Sample attached:
Just deploy the testEAR to was8.5let me know if you need any furthur information
thanks
Attachments:
You must be logged in to view attached files.
support-pradeepMemberviswamy2k,
I have tried deploying the application you have attached in WAS 8.5 outside MyEclipse and I see the same error. When I looked into your application I found that the jar files in the lib folder are causing this issue. Because when you try to deploy the application in addition to the jar files in the lib, TestEJB21.jar and TestEJB31.jar are also present.
Take a look at the structure of your application in the screenshot attached.
Can you please remove the jar files from lib folder of EAR project and try deploying ?
Let us know how it works for you.
Attachments:
You must be logged in to view attached files.
viswamy2kParticipantthanks,
We need these jars as part EAR lib and same way we are using from long but after upgrading to MyElcipseBlue10.6 with WAS8.5 we are facing this problem,
So, it will be good if you can suggest any solution for this
thanks in advance
-viswa
support-pradeepMemberviswamy2k,
The stack trace suggests that the issue is with WAS 8.5 EJB deploy tool. We cannot provide any solution as it is WAS 8.5 issue.
As a workaround from our end you can use EJB Deploy tool within MyEclipse.
Here are the steps:1) Right click on EAR project -> Properties -> MyEclipse -> EAR -> Unselect “Run EJBDeploy tool”
2) Right click on EAR project -> MyEclipse -> Run EJBDeploy. If the EJB deploy is not already configured then it will ask you to do so. Select the appropriate server in the wizard and proceed.
3) Once the EJB deploy tool is successfully run, deploy your application in WAS 8.5.Let us know how it works for you.
-
AuthorPosts