[mnovak5528]

I installed WebSphere 8 (8.0.2.20120119_1958) on my PC (running WinXT SP3) along with MyEclipse Blue 9.1-Blue-20110701. I set up a profile, running as a manual service because it would not start otherwise. I was able to start the server without a deployment. But when I deployed my application, the deployment stalled for a long time (ran overnight so I don’t know how long) and then failed with a Java OutOfMemory error. On rerunning the deployment, it again ran overnight and never completed.

I am moving my development environment from one PC to another. On my old PC, I had this application deployed and running on WebSphere 6.1.0_39, but I am trying WebSphere 8 on the new PC for the first time.

Can you help me troubleshoot this deployment problem on my new PC?

Attachments:

You must be logged in to view attached files.

[Brian Fernandes]

mnovak,

1) What installation of WAS 8 are you using? Is this the developer edition or the complete production version?

2) What deployment mode are you using for your application? Classic, Enhanced or In-workspace?

3) How large is your application (approximately, if, for instance, you had exported it as an EAR)

4) Our WAS 8 support was significantly improved in 10.0; given the nature of your problem, I’m unsure if moving to 10.0 would fix the issue, but it is definitely something that must be tried. We changed the way in which WAS 8 is started.

[mnovak5528]

We are set up as follows:

WebSphere 8.0.2.20120119_1958 Developer edition
Classic Deployment Mode
EAR file is 10.1Mb

I would be happy to try version 10. Does my current subscription apply to version 10?
Do you think I should fully uninstall version 9 before going to 10?

[Brian Fernandes]

mnovak,

1) You don’t need to uninstall MyEclipse 9, you can install 10 alongside 9.
2) Our Subscriptions are time based , not version based – you can use them for any version of the product, so your current license would allow you to use 10.0 without issue.
3) You could also think of configuring the profile to use the in-workspace mode, it might deploy the project faster in your case.

[mnovak5528]

I had the same problem deploying in MyEclipse Blue in Classic Mode. Using In-Workspace deployment, I got a lot of out of memory errors.

Attachments:

You must be logged in to view attached files.

[mnovak5528]

I have tried all of the ideas you have given to me so far without success (see last post). Do you have any other ideas?

[Brian Fernandes]

mnovak,

Sorry I missed your last post. Can you confirm that you used MyEclipse 10 for testing the in-workspace and the classic modes and not the MyEclipse 9 release? 10.1 was released this Monday, so if you haven’t already tried 10.0 yet, I would recommend 10.1 instead (though it did not specifically have any fixes pertaining to this issue.

The OOM issues for an application that is only around 10 MB in size is certainly very odd, correspondingly, deployment, even in the classic mode, should not take much time.

1) Have you changed the application at all to deploy it to WAS 8? Can it still be deployed to WAS 6 in its current form?
2) Did you notice the point at which the stall took place during the deployment? You could check the last message reported in the Console at this point.
3) What is the structure of your application – for example is it an EAR with one Web and EJB module each?

[mnovak5528]

I ran the deploy using 10.1, both In Workspace and Classic Modes. I have MyEclipse 9 also installed on my PC, but these deployments were run on 10.1.

We have not changed the application to deploy to WebSphere 8. We initially had a similar problem deploying to WAS 6.1, reported to you when we first started using MyEclipse Blue. That problem was eventually resolved by upgrading our WebSphere Application Server to release 6.1.0_39. After that, deployments under 6.1 work fine.

I have attached a copy of the deployment log, which does not change beyond this point after hanging.

I have also attached a document describing how we set up MyEclipse Blue and WAS 8.

The application has no EJBs.

Your help is greatly appreciated.

Attachments:

You must be logged in to view attached files.

[Brian Fernandes]

mnovak,

I’m afraid the logs didn’t help much.

You stated that the application had not been migrated in any way to work with WebSphere 8 – does it still reference WebSphere 6.1 libraries by any chance? Could you attach the .classpath file here?

Going through your document, it also appears that you are adding 6.1 specific libraries to the project in step 6.a.i for instance – is this document current for your attempts to deploy to WebSphere 8 too?

[ajsiegle]

I am having the same issue. I even modified the jvm settings of my server to have init heap of 768 and max of 1024, but it did not help. Ours is also a migration project, and I have modified the project already to run on WAS8.

Blue:
MyEclipse Blue Edition
Version: 10.1 Blue
Build id: 10.1-Blue-20120316

WAS 8 for developers:
WebSphere Platform 8.0.0.3 [BASE 8.0.0.3 cf031212.03] running with process name vmwmyeclipseNode02Cell\vmwmyeclipseNode02\Blue and process id 2356
Host Operating System is Windows XP, version 5.1
Java version = 1.6.0, Java Compiler = j9jit26, Java VM name = IBM J9 VM

When I try to deploy, the console messages are below:

WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: “[C:\Program Files\IBM\WebSphere\AppServer\profiles\Blue\installableApps\aquitecdev.ear, vmwmyeclipseNode02Cell, vmwmyeclipseNode02, Blue, aquitecdev, {{“aquitecdev_web.war” “aquitecdev_web.war,WEB-INF/web.xml” default_host}}, {{.* .* AppDeploymentOption.Yes 1}}, false, false, false, C:/Program Files/MyEclipse Blue Edition/MyEclipse Blue Edition 10/configuration/org.eclipse.osgi/bundles/19/1/.cp/scriptutil/scriptutil.jar, none, 1.4, true, none]”
C:\Program Files\IBM\WebSphere\AppServer\profiles\Blue\installableApps\aquitecdev.ear
vmwmyeclipseNode02Cell
vmwmyeclipseNode02
Blue
aquitecdev
{“aquitecdev_web.war” “aquitecdev_web.war,WEB-INF/web.xml” default_host}
{.* .* AppDeploymentOption.Yes 1}
-nopreCompileJSPs -distributeApp -server “Blue” -useMetaDataFromBinary -nodeployejb -appname “aquitecdev” -createMBeansForResources -reloadEnabled -reloadInterval 1 -deployws -validateinstall off -processEmbeddedConfig -filepermission .*.dll=755#.*.so=755#.*.a=755#.*.sl=755 -buildVersion Unknown -noallowDispatchRemoteInclude -noallowServiceRemoteInclude -MapWebModToVH {{“aquitecdev_web.war” “aquitecdev_web.war,WEB-INF/web.xml” default_host}} -JSPReloadForWebMod {{.* .* AppDeploymentOption.Yes 1}}
false
false
false
C:/Program Files/MyEclipse Blue Edition/MyEclipse Blue Edition 10/configuration/org.eclipse.osgi/bundles/19/1/.cp/scriptutil/scriptutil.jar

-nodeployejb
1.4
-processEmbeddedConfig
JVMDUMP039I Processing dump event “systhrow”, detail “java/lang/OutOfMemoryError” at 2012/05/25 13:11:27 – please wait.
JVMDUMP032I JVM requested System dump using ‘C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\core.20120525.131127.3152.0001.dmp’ in response to an event
JVMDUMP010I System dump written to C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\core.20120525.131127.3152.0001.dmp
JVMDUMP032I JVM requested Heap dump using ‘C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\heapdump.20120525.131127.3152.0002.phd’ in response to an event
JVMDUMP010I Heap dump written to C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\heapdump.20120525.131127.3152.0002.phd
JVMDUMP032I JVM requested Java dump using ‘C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\javacore.20120525.131127.3152.0003.txt’ in response to an event
JVMDUMP010I Java dump written to C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\javacore.20120525.131127.3152.0003.txt
JVMDUMP032I JVM requested Snap dump using ‘C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\Snap.20120525.131127.3152.0004.trc’ in response to an event
JVMDUMP010I Snap dump written to C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\Snap.20120525.131127.3152.0004.trc
JVMDUMP013I Processed dump event “systhrow”, detail “java/lang/OutOfMemoryError”.
JVMDUMP039I Processing dump event “systhrow”, detail “java/lang/OutOfMemoryError” at 2012/05/25 13:12:21 – please wait.
JVMDUMP032I JVM requested Heap dump using ‘C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\heapdump.20120525.131221.3152.0005.phd’ in response to an event
JVMDUMP010I Heap dump written to C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\heapdump.20120525.131221.3152.0005.phd
JVMDUMP032I JVM requested Java dump using ‘C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\javacore.20120525.131221.3152.0006.txt’ in response to an event
JVMDUMP010I Java dump written to C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\javacore.20120525.131221.3152.0006.txt
JVMDUMP032I JVM requested Snap dump using ‘C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\Snap.20120525.131221.3152.0007.trc’ in response to an event
JVMDUMP010I Snap dump written to C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\Snap.20120525.131221.3152.0007.trc
JVMDUMP013I Processed dump event “systhrow”, detail “java/lang/OutOfMemoryError”.
java.lang.OutOfMemoryError
at java.util.HashMap.createHashedEntry(HashMap.java:651)
at java.util.HashMap.putImpl(HashMap.java:627)
at java.util.HashMap.put(HashMap.java:607)
at java.util.HashSet.add(HashSet.java:95)
at org.eclipse.core.internal.jobs.JobManager.changeState(JobManager.java:328)
at org.eclipse.core.internal.jobs.JobManager.nextJob(JobManager.java:833)
at org.eclipse.core.internal.jobs.JobManager.startJob(JobManager.java:1103)
at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:219)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:51)
WASX7017E: Exception received while running file “C:\Program Files\MyEclipse Blue Edition\Common\plugins\com.genuitec.eclipse.blue.websphere8_9.0.0.me201203060843\installEAR.jacl”; exception information: com.ibm.websphere.management.application.client.AppDeploymentException: com.ibm.websphere.management.application.client.AppDeploymentException: [Root exception is java.lang.OutOfMemoryError]
java.lang.OutOfMemoryError: java.lang.OutOfMemoryError

[support-swapna]

ajsiegle,

Sorry that you are seeing this issue.

Can you answer some more questions for us ?

1. What deployment mode are you using for your application? Classic, Enhanced or In-workspace?

2. How large is your application (approximately, if, for instance, you had exported it as an EAR)

3. What is the structure of your application ?

4. On which version of WAS was this project deployed earlier?

5. Can you check if the in-workspace deployment mode works better for you?

6. Could you please attach the .classpath file here?

[ajsiegle]

1. Classic
2. 6MB
3. Ear has one web project, no ejbs
4. WAS 6.1
5. Tried to use in-workspace, it failed. Got this out of the log:

[[6/1/12 16:46:51:925 CDT] 0000001c wtp W org.eclipse.jst.j2ee.commonarchivecore.looseconfig.internal.LooseConfigRegister
loadResource Failed to load loose register
[ file:/C:/workspace/.metadata/.plugins/com.genuitec.eclipse.blue.websphere/aquitecdev.websphere8Server_Blue.xml ]
[ org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature ‘version’ not found. (file:/C:/workspace/.metadata/.plugins/com.genuitec.eclipse.blue.websphere/aquitecdev.websphere8Server_Blue.xml, 2, 375) ]
[6/1/12 16:46:51:925 CDT] 0000001c wtp W org.eclipse.jst.j2ee.commonarchivecore.looseconfig.internal.LooseConfigRegister
loadResource Exception
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1$DiagnosticWrappedException: org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature ‘version’ not found. (file:/C:/workspace/.metadata/.plugins/com.genuitec.eclipse.blue.websphere/aquitecdev.websphere8Server_Blue.xml, 2, 375)
at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.handleDemandLoadException(ResourceSetImpl.java:307)
at

6. Attached

Attachments:

You must be logged in to view attached files.

[support-swapna]

ajsiegle,

Thank you for the details.

Can you check if you can deploy this project to WAS 8 outside of MyEclipse Blue without any issues ?

[ajsiegle]

Here is what I noticed. I manually added the IBM runtime jars to my classpath since Blue couldn’t find any of them. When I exported the ear to install manually, the jars were all put into the war, which now was huge compared to my normal ear. I took them out of the war and then deployed my ear manually via the console, which worked ok.

Are these jars causing the out of memory error?

[support-piotr]

ajsiegle.

Thanks for trying that out! Since you’ve manually added jars to the classpath, they were, by default, packed into EAR/WAR. Please modify workspace preferences. Go to: Window > Preferences > MyEclipse > Java Enterprise Projects > Web Project. Here you should uncheck option “JARs from the build path”. This should prevent MyEclipse from packing runtime (and any other from the classpath) Jars into EAR. We are currently working on providing flexible runtimes for projects, however such feature will be available in ME11 only.

However, in case, that you have some others jars attached to the build path, you have two options:
1. You can use “Deployment assembly” to specify what and where should be packed into war (Project > Properties > MyEclipse > Deployment Assembly)
2. You can create User Library for WebSphere Runtime. Go to: Window -> Preferences -> Java -> Build Path -> User Libraries, configure User Library and add it to project path (Project -> Properties > Java build path -> Libraries -> Add library -> Select User library). Go once again to Deployment Settings (Window > Preferences > MyEclipse > Java Enterprise Projects > Web Project) and uncheck “Jars from users libraries” and “User library jars exported from dependent java projects” making sure, that two others are checked, in that case.

I hope that this solution will help you with the problem. Let us know if your archive is now correctly created and if you can deploy it manually and from ME.

[Author]

Posts