[striebhz]

Hi,

after some OutOfMemoryErrors i changed the memory settings in the file MyEclipse Blue Edition 10\myeclipse-blue.ini to

-Xmx1024m
-XX:MaxPermSize=512m
-XX:ReservedCodeCacheSize=128m

Surprisingly, the deployment on WAS 8.0 fails after the change. MyEclipse seems to package the .ear, but in “installedApps” the .ear has a size of 0 bytes.

I couldn’t find any logs or error message which lead me to the problem but after reverting the changes the deployment works fine.
But how can I increase the memory now?

[striebhz]

ah it’s not “installedApps” but “installableApps”

[support-swapna]

striebhz,

Sorry that you are seeing issues.

1. Can you please let us know at what point did you come across the OutOfMemory errors ? Did you see them when working with any of the editors or when deploying a project to Websphere 8.0?

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. If you are looking at increasing the memory settings for MyEclipse, then the following settings may be preferable to the defaults.

Code:
-vmargs
-Xmx768m
-XX:MaxPermSize=384m

Let us know how it works for you.

[striebhz]

The OutOfMemory errors mainly occur when developping Java (of course) and parallel JSF-XHTML-Pages. So I can deploy without increasing memory if I don’t open any XHTML file, but that’s not a very useful workaround.

We are using enhanced deploy mode.

It’s difficult to say how large the project is – the EAR ist about 60 MB but with many dependent Jars. There are about 10 EJB modules and a WAR project.

The settings with 768m works, but there must be a way to set it higher because the project will grow fast and I think won’t be sufficient soon.

[support-tony]

striebhz,

We couldn’t replicate the problem, though we haven’t tried with exactly the same set-up as you. The memory settings that you have now should be fine for even large projects though I agree, you should be able to run with higher settings.

We are trying to replicate your particular set-up to see if the problem is specific to that. In the meantime, could you post your installation information, which can be found at MyEclipse->Installation Summary->Installation Details, and your myeclipse-blue.ini file. If there is any other information that you think is relevant, please post that also.

[striebhz]

Sorry for the delayed response, I have been on holiday. 🙂

An important information is perhaps that I’m working on a 64 bit OS with a 32 bit MyEclipse.

Installation Details:

*** Date: 
Mittwoch, 3. Oktober 2012 15:22 Uhr MESZ

*** System properties:
OS=WindowsVista
OS version=6.1.0
OS arch=x86
Profile arch=x86
Window system=win32
Java version=1.6.0_13
Workspace=file:/X:/gem_current/
VM Args=-Xmx768m
-XX:MaxPermSize=384m
-XX:ReservedCodeCacheSize=64m
-Dosgi.nls.warnings=ignore
-Djava.class.path=D:\MYECLI~1\MYECLI~1\../Common/plugins/ORB7B5~1.JAR



*** Subscription information
Product Id: E3MB (MyEclipse Blue Subscription)
License version: 3.0
Full Maintenance Included
Subscription expiration date (YYYYMMDD): 20130808
Number of users: 1

*** Eclipse details:
MyEclipse Blue Edition

Version: 10.6 Blue
Build id: 10.6-Blue-20120727


Blueprint: MyEclipse Blue Edition 10

com.genuitec.myeclipse.blue.feature - 10.6.0.me201207261914
com.genuitec.myeclipse.database - 10.6.0.me201207261914
com.genuitec.myeclipse.db2 - 10.6.0.me201207261914
com.genuitec.myeclipse.desktop - 10.6.0.me201207261914
com.genuitec.myeclipse.editor - 10.6.0.me201207261914
com.genuitec.myeclipse.geronimo - 10.6.0.me201207261914
com.genuitec.myeclipse.glassfish - 10.6.0.me201207261914
com.genuitec.myeclipse.icefaces.feature - 10.6.0.me201207261914
com.genuitec.myeclipse.iedebugger - 10.6.0.me201207261914
com.genuitec.myeclipse.imageeditor - 10.6.0.me201207261914
com.genuitec.myeclipse.jboss - 10.6.0.me201207261914
com.genuitec.myeclipse.jetty - 10.6.0.me201207261914
com.genuitec.myeclipse.jonas - 10.6.0.me201207261914
com.genuitec.myeclipse.jrun - 10.6.0.me201207261914
com.genuitec.myeclipse.jsf - 10.6.0.me201207261914
com.genuitec.myeclipse.matisse - 10.6.0.me201207261914
com.genuitec.myeclipse.maven - 10.6.0.me201207261914
com.genuitec.myeclipse.oracle - 10.6.0.me201207261914
com.genuitec.myeclipse.orion - 10.6.0.me201207261914
com.genuitec.myeclipse.persistence - 10.6.0.me201207261914
com.genuitec.myeclipse.pulse - 10.6.0.me201207261914
com.genuitec.myeclipse.reports - 10.6.0.me201207261914
com.genuitec.myeclipse.resin - 10.6.0.me201207261914
com.genuitec.myeclipse.struts - 10.6.0.me201207261914
com.genuitec.myeclipse.sun - 10.6.0.me201207261914
com.genuitec.myeclipse.tomcat - 10.6.0.me201207261914
com.genuitec.myeclipse.uml2 - 10.6.0.me201207261914
com.genuitec.myeclipse.visualvm - 10.6.0.me201207261914
com.genuitec.myeclipse.visualvm.server - 10.6.0.me201207261914
com.genuitec.myeclipse.weblogic - 10.6.0.me201207261914
com.genuitec.myeclipse.ws - 10.6.0.me201207261914
com.genuitec.myeclipse.ws.blue - 10.6.0.me201207261914
org.eclipse.birt - 2.6.1.me201207261914
org.eclipse.datatools.connectivity.feature - 1.9.0.me201207261914
org.eclipse.datatools.enablement.feature - 1.9.0.me201207261914
org.eclipse.datatools.modelbase.feature - 1.9.0.v201106031100-77078CcNBHCBYKYEbNV
org.eclipse.datatools.sqldevtools.feature - 1.9.0.me201207261914
org.eclipse.emf - 2.7.0.v20110606-0949
org.eclipse.gef - 3.7.0.v20110425-2050-777D-81B2Bz0685C3A6E34272
org.eclipse.graphiti.feature - 0.8.0.v20110607-1252
org.eclipse.jpt.jpa.feature - 3.0.0.me201207261914
org.eclipse.jpt.jpadiagrameditor.feature - 1.0.0.me201207261914
org.eclipse.jst.common.fproj.enablement.jdt - 3.3.0.me201207261914
org.eclipse.jst.enterprise_ui.feature - 3.3.0.me201207261914
org.eclipse.jst.server_adapters.ext.feature - 3.3.0.me201207261914
org.eclipse.jst.server_adapters.feature - 3.2.100.me201207261914
org.eclipse.jst.server_ui.feature - 3.3.0.me201207261914
org.eclipse.jst.ws.axis2tools.feature - 1.1.200.me201207261914
org.eclipse.m2e.feature - 1.0.0.me201207261914
org.eclipse.sapphire.platform - 0.3.0.201106221325
org.eclipse.wst.common.fproj - 3.3.0.me201207261914
org.eclipse.wst.server_adapters.feature - 3.2.100.me201207261914
org.eclipse.xsd - 2.7.0.v20110606-0949
org.springframework.ide.eclipse.feature - 2.9.1.me201207261914


fr.obeo.acceleo.bridge.feature - 2.6.0.200906261742
org.eclipse.cvs - 1.3.100.v20110520-0800-7B78FHl9VF7BD7KBM4GP9C
org.eclipse.draw2d - 3.7.0.v20110425-2050-46-7w3122153603161
org.eclipse.equinox.p2.core.feature - 1.0.1.v20110906-1605-8290FZ9FVKHVRKtmx3fpNuo02129
org.eclipse.equinox.p2.extras.feature - 1.0.1.v20110906-1605-7A4FD4DiVOMap8cHSc6vPuny4gqO
org.eclipse.equinox.p2.rcp.feature - 1.0.1.v20110906-1605-782EqBqNKGVkiV-PUsgz-uny4gqO
org.eclipse.equinox.p2.user.ui - 2.1.2.R37x_v20110815-1155-6-Bk8pYWZz0qUTX5I15GZWwbXkrl
org.eclipse.help - 1.3.0.v20110530-0844-7i7uFFmFFl8nvqbDpEqTvx
org.eclipse.jdt - 3.7.2.v20120120-1414-7z8gFcuFMP7BW5XTz0jLTnz0l9B1
org.eclipse.jsf.feature - 3.3.0.me201207261914
org.eclipse.ocl - 3.1.0.v20110606-1427
org.eclipse.pde - 3.7.2.v20120120-1420-7b7rFUOFEx2Xnqafnpz0E--0
org.eclipse.platform - 3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q
org.eclipse.rcp - 3.7.2.v20120120-1424-9DB5FmnFq5JCf1UA38R-kz0S0272


Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
D:\MyEclipse\MyEclipse Blue Edition 10\myeclipse-blue.exe
-name
Myeclipse-blue
--launcher.library
D:\MyEclipse\MyEclipse Blue Edition 10\../Common/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_4.2.0.v201201111650\eclipse_4201.dll
-startup
D:\MyEclipse\MyEclipse Blue Edition 10\../Common/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
-install
D:/MyEclipse/MyEclipse Blue Edition 10
-vm
D:/MyEclipse/Common/binary/com.sun.java.jdk.win32.x86_1.6.0.013/jre/bin/client/jvm.dll

myeclipse-blue.ini (I changed nothing but the memory settings):

#utf8 (do not remove)
#utf8 (do not remove)
-startup
../Common/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
../Common/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_4.2.0.v201201111650
-install
D:/MyEclipse/MyEclipse Blue Edition 10
-vm
D:/MyEclipse/Common/binary/com.sun.java.jdk.win32.x86_1.6.0.013/jre/bin/client/jvm.dll
-vmargs
-Xmx768m
-XX:MaxPermSize=384m
-XX:ReservedCodeCacheSize=64m
-Dosgi.nls.warnings=ignore

[support-tony]

striebhz,

Thanks for posting the details; I hope you had a good holiday!

Well, I think I’ve replicated your set up exactly, 32 bit MyEclipse Blue on 64 bit Windows 7, deploying to WAS 8.0. However, I can’t get the deployment to fail on my setup, though I’m just using a minimal application with one minimal EJB module and one minimal Web module. The EAR file generated doesn’t have a zero size.

Some things to try, with the memory settings as per your first post:

1. I did notice that your myeclipse-blue.ini file is not quite the same as mine, as freshly installed. There is a missing configuration specification, though even when I commented that out, I still didn’t get a failure. However, if you could add the following to the .ini file, just before the -vmargs line:

   -configuration
   D:/MyEclipse/MyEclipse Blue Edition 10

   This will at least show whether the default configuration is different from the above, and causing problems.

2. Try exporting your enterprise application as an EAR and see if it contains anything (you could also try installing the EAR from the WAS admin console).
3. Try a minimal enterprise application (just create an enterprise application and get the wizard to create EJB and WEB projects) and see if that deploys OK.

Let us know if any of this helps.

[striebhz]

Hi,

changing the INI file did not solve the problem. The problem remains and sometimes, MyEclipse even crashes with the high memory settings.

Try exporting your enterprise application as an EAR and see if it contains anything (you could also try installing the EAR from the WAS admin console).

I’m sorry but I don’t know how to export the EAR.

Try a minimal enterprise application (just create an enterprise application and get the wizard to create EJB and WEB projects) and see if that deploys OK.

Uhm… this might take some time. I’ll try it later.
You were right, setting the memory to 768 / 384 / 64 seems to work for big projects too, so I’m not in a hurry for that.

[support-tony]

striebhz,

To export to an EAR file, select the Export menu item from the File menu Next, expand the Java EE item and select EAR (If you see two EAR entries, select the one that includes “MyEclipse”) and click Next. Now select the enterprise project you wish to export and type in the full path name of the file you want to create (or you can browse to a location and enter a file name there). Click Finish to complete the export. Now check that the EAR file is not empty.

However, if you’re happy with your setup at the moment, that’s fine. If you want, or need, to get this issue resolved in the future, please try the above export and also try to replicate the problem with a basic Enterprise Application Project (to start, you can just let MyEclipse generate everything for you, including an EJB and Web project as part of the Enterprise Application Project creation).

[Author]

Posts