- This topic has 16 replies, 4 voices, and was last updated 14 years, 8 months ago by
.
-
Posts
-
I have some web projects that I have been developing in prototype form on Tomcat. I’m now moving them into real code, which will be deployed on WebSphere 7, so I have just downloaded MyEclipse 8.5.
I created an Enterprise Application Project, and added the web modules to the Ear. When I try to add the ear to WAS, it just gets an exception as follows:
ASX7209I: Connected to process “server1” on node COLINSW7LTNode01 using SOAP connector; The type of process is: UnManagedProcess
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: “[C:\\software\\WebSphere\\AppServer\\profiles\\AppSrv01\\installableApps\\GatewayApp.ear, COLINSW7LTNode01Cell, COLINSW7LTNode01, server1, GatewayApp, {{“SCGSynchroniser.war” “SCGSynchroniser.war,WEB-INF/web.xml” default_host}}, {{.* .* AppDeploymentOption.Yes 1}}, true, false, true, C:/software/Genuitec/MyEclipse Blue Edition 8.5/configuration/org.eclipse.osgi/bundles/10/1/.cp/scriptutil/scriptutil.jar, 1.4]”
C:\software\WebSphere\AppServer\profiles\AppSrv01\installableApps\GatewayApp.ear
COLINSW7LTNode01Cell
COLINSW7LTNode01
server1
GatewayApp
{“SCGSynchroniser.war” “SCGSynchroniser.war,WEB-INF/web.xml” default_host}
{.* .* AppDeploymentOption.Yes 1}
-nopreCompileJSPs -distributeApp -useMetaDataFromBinary -nodeployejb -appname “GatewayApp” -createMBeansForResources -reloadEnabled -reloadInterval 1 -deployws -validateinstall off -noprocessEmbeddedConfig -filepermission .*.dll=755#.*.so=755#.*.a=755#.*.sl=755 -buildVersion Unknown -noallowDispatchRemoteInclude -noallowServiceRemoteInclude -MapWebModToVH {{“SCGSynchroniser.war” “SCGSynchroniser.war,WEB-INF/web.xml” default_host}} -JSPReloadForWebMod {{.* .* AppDeploymentOption.Yes 1}}
true
false
true
C:/software/Genuitec/MyEclipse Blue Edition 8.5/configuration/org.eclipse.osgi/bundles/10/1/.cp/scriptutil/scriptutil.jar
1.4
-nodeployejbWASX7017E: Exception received while running file “C:\software\Genuitec\Common\plugins\com.genuitec.eclipse.blue.websphere7_8.5.0.me201003250241\installEAR.jacl”; exception information: com.ibm.websphere.management.application.client.AppDeploymentException: com.ibm.websphere.management.application.client.AppDeploymentException: ADMA0092E: An unexpected exception occurred while preparing task AppDeploymentOptions. Check the server machine First Failure Data Capture tool (FFDC) for more information. [Root exception is org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsException: index=0, size=0]
org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsException: org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsException: index=0, size=0The app shows up under the WAS server in MyEclipse, but WAS doesn’t know anything about the app, and compains if I try to remove the deployment.
Any ideas what is going on? This is delaying my project, so I need an urgent response.
ColinSharples,
I could not replicate this at my end, can you give some more information?
1. Can you copy paste your installation details from MyEclipse > Installation Summary > Installation Details?
2. Can you list out the steps in detail to replicate the above issue?
3. How did you deploy your application? Packaged/Exploded mode?
4. Did you set “Run Application Server Proces as a Windows Service” when installing Websphere?
Can you try the workaround given in the following link –
http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14286110&tstart=0
Let me know if that helps.*** Date:
Thursday, 1 April 2010 10:58:23 AM NZDT** System properties:
OS=WindowsVista
OS version=6.1.0
Java version=1.6.0_13*** MyEclipse details:
MyEclipse Blue Edition
Version: 8.5 Blue
Build id: 8.5-Blue-20100319*** Eclipse details:
MyEclipse Blue EditionVersion: 8.5 Blue
Build id: 8.5-Blue-20100319Eclipse Platform
Version: 3.5.2.R35x_v20100210-0800-9hEiFzmFst-TiEn9hNYgDWg1XN8ulH_JvCNGB
Build id: M20100211-1343Eclipse Java Development Tools
Version: 3.5.2.r352_v20100108-7r88FEwFI0WTuoBl0iaG0tyhfZH6
Build id: M20100211-1343Eclipse Plug-in Development Environment
Version: 3.5.2.R35x_v20100119-7Z7_FA2FDX-aXQYWqYDBz-z0qufo
Build id: M20100211-1343Eclipse Graphical Editing Framework GEF
Version: 3.5.2.v20100111-1352-777928194B66D5D476C33B2A
Build id: 201001111753Eclipse RCP
Version: 3.5.2.R35x_v20100119-9SA0FxwFnoCU5XxWItFdXXb27BA6
Build id: M20100211-1343Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\software\Genuitec\MyEclipse Blue Edition 8.5\myeclipse-blue.exe
-name
Myeclipse-blue
–launcher.library
C:\software\Genuitec\MyEclipse Blue Edition 8.5\../Common/plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519\eclipse_1206.dll
-startup
C:\software\Genuitec\MyEclipse Blue Edition 8.5\../Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
-install
C:/software/Genuitec/MyEclipse Blue Edition 8.5
-configuration
configuration
-vm
C:/software/Genuitec/Common/binary/com.sun.java.jdk.win32.x86_1.6.0.013/jre/bin/client/jvm.dllWell, removing the service seemed to help for a while, but now the exception has happened again. I had rebuilt my app from scratch, creating new projects and copying the old code into them. I did manage to get the app deployed, but then I moved jar files from the Ear project back down into the web modules, and the next time I started the server, it had lost the app. I tried to redeploy, and got the same exception as before.
This is now holding up my project – if I can’t resolve this soon, we are going to have to ditch MyEclipse.
ColinSharples,
Can you try re-installing Websphere? Please follow the steps as given in the following tutorial – http://www.myeclipseide.com/documentation/quickstarts/websphere6/
This tutorial is based on MyEclipse and WAS 6 but the same process can be followed for MyEclipse Blue and WAS 7
Let me know if that helps.I definitely think it is something to do with the way MyEclipse is preparing the ear file, because if I prepare the ear file with Ant, and then deploy manually into WAS, it works fine. It’s only when I am trying to deploy from MyEclipse that I get the problem.
Okay, so the problem seems to relate to the ibmconfig that MyEclipse is adding. If I build the ear file manually without the ibmconfig folder, it works okay, but if I include the ibmconfig in the ear file, then I get the same exception. Something about the ibmconfig must be causing the problem.
I need my application to use classloader per module and parent last loading, so maybe it’s something to do with that? If I install manually without the ibmconfig, I have to go into the app after it has been installed and manually change the classloader settings, then everything works fine.
I found a workaround. Even though the deployment fails, the app still shows up under the WAS server in the servers view. I then manually installed the app through the admin console, and then back in MyEclipse clicked Redeploy/Reload. This time the deployment worked, and now it is picking up the changes I make in MyEclipse.
I’d still like to know what it is in the ibmconfig that is causing it to fail, though.
I think this is related to the ibmconfig that MyEclipse is creating. Try the following to see if you can recreate:
Create a new enterprise app and four web modules.
Add some jar files to the lib directory of the enterprise app.
Reference the jar files on the build path of each web module, and add the jar files to the web module manifests (I had to do this manually, because the New Module Manifests action didn’t seem to work)
Open the enterprise app application.xml. On the Application Configuration tab, change the classloader mode to PARENT_LAST and WAS Classloader Policy to MODULE. On each of the web modules, also change Classloader mode to PARENT_LAST, and save application.xml.
Deploy the app to WAS 7 – this is where I get the exception.
If I include the ibmconfig folder in my manual build, I get the same exception when deploying directly through the admin console, but excluding ibmconfig makes it work okay – I just have to manually change the classloader mode on the modules after I deploy it.
Colin,
I appreciate your detailed research into this issue and the workarounds that you have found – will certainly speed up investigation. Both the WAS issues that you reported have been escalated to our Blue team who are looking at it right now.
What is your EAR composed of? Just multiple web modules with no EJB modules?
Also, what are the locations of your WAS installation directory and your profile folder?
Yes, it is just web modules.
WAS is installed in C:/software/WebSphere/AppServer, and the profile is the default one created when I installed – AppSrv01.
Colin thanks for the quick response – I assume AppSrv01 is at C:/software/WebSphere/AppServer/profiles/AppSrv01?
Colin,
Did / do you use the “WebSphere Application Editor” to edit your application.xml? It’s our new multi-page form editor that we introduced with MyEclipse 8.5. We just noticed a bug where it seems to be writing out an incomplete deployment.xml file which could be causing your issues.
Suggested steps:
1) Close all editors.
2) Find the following file in your project.
/META-INF/ibmconfig/cells/defaultCell/applications/defaultApp/deployments/defaultApp/deployment.xml
3) Right click the file and choose Open With > MyEclipse XML Editor and change the first line from<appdeployment:Deployment xmi:id="Deployment_1262775196208">to
<appdeployment:Deployment xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:appdeployment="http://www.ibm.com/websphere/appserver/schemas/5.0/appdeployment.xmi" xmi:id="Deployment_1262775196208">and save the file.
If you deploy your project now, does it work as expected? As an alternative quick test you could simply delete the deployment.xml file and try a deployment as well to make sure the erroneous file is not being deployed with your project.
Once you make the change to the header of deployment.xml (please note that this file will be created when you switch to the configuration tab of the WebSphere Application editor) then you can continue using the editor without issue.
Please let us know if this fixes the problem for you.
