[ColinSharples]

Following on from the problems I had earlier with deploying to WAS 7 from MyEclipse. I now have the application installed, and I have been able to do redeploys. However, about every 3rd or 4th time I do a redeploy, WAS ends up with an out of memory error. Once that has happened, the only way I can recover is to remove the deployment, and then go through the workaround I described before (deploy through admin console and then update from MyEclipse).

This is causing significant delays on my project, and I can’t afford the delays any more. I need a resolution to this as soon as possible.

[support-shalini]

ColinSharples,
Can you give some more information?
1. Can you copy paste your installation details from MyEclipse > Installation Summary > Installation Details?
2. Are there any errors in the log file located at workspace dir > .metadata > .log when you redeploy your application?
please clear your log file, save it and then redeploy the application before you look for errors logged.
3. What are the Optional Java VM arguments when you select Window > Preferences > MyEclipse > Servers > Websphere 7.0, select your server instance > edit and click next in the new wizard to go to VM arguments
Can you try pasting the following under Optional Java VM arguments and check if that works for you
-Xscmx50M -Xms50m -Xmx256m
Also, are there any errors logged in the deployment log when you redeploy your application? Right click on your server in the servers view and from the context menu select “View Deployment log” and check if there are any errors logged.

[ColinSharples]

*** Date:
Tuesday, 27 April 2010 3:49:26 PM NZST

** 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 Edition

Version: 8.5 Blue
Build id: 8.5-Blue-20100319

Eclipse Platform

Version: 3.5.2.R35x_v20100210-0800-9hEiFzmFst-TiEn9hNYgDWg1XN8ulH_JvCNGB
Build id: M20100211-1343

Eclipse Java Development Tools

Version: 3.5.2.r352_v20100108-7r88FEwFI0WTuoBl0iaG0tyhfZH6
Build id: M20100211-1343

Eclipse Plug-in Development Environment

Version: 3.5.2.R35x_v20100119-7Z7_FA2FDX-aXQYWqYDBz-z0qufo
Build id: M20100211-1343

Eclipse Graphical Editing Framework GEF

Version: 3.5.2.v20100111-1352-777928194B66D5D476C33B2A
Build id: 201001111753

Eclipse RCP

Version: 3.5.2.R35x_v20100119-9SA0FxwFnoCU5XxWItFdXXb27BA6
Build id: M20100211-1343

Eclipse 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.dll

[ColinSharples]

Yes, I have used those JVM arguments, although I have specified 1536 as the max heap size – I have 4GB RAM, so it certainly should be able to handle 1536.

[support-shalini]

ColinSharples,
Are there any errors in the log file or in the deployment log?

[ColinSharples]

I removed the JVM arguments from the launch config, and set the heap size parameters directly in the WAS app console, and that seems to have fixed it. Perhaps it was the -Xscmx parameter that caused the issue? From the WAS documentation it appears that you shouldn’t use this unless you also specify -Xshareclasses.

I still have the original problem with add deployment from MyEclipse getting an exception – any progress on that?

[Author]

Posts