[BethJackson14]

WHen I bring it up it takes about 10 minutes and then after it is up it hangs with (NOT RESPONDING) when I click on anything. Sometimes after it is up for a long time it will start responding quicker but wiill hang again.
*** Date:
Wednesday, September 18, 2013 9:08:57 PM CDT

*** System properties:
OS=Windows7
OS version=6.1.0
OS arch=x86
Profile arch=x86
Window system=win32
Java version=1.6.0_43
Workspace=file:/C:/Users/e1032606/Workspaces/Insight Workspace/
VM Args=-Xmx512m
-XX:MaxPermSize=256m
-XX:ReservedCodeCacheSize=64m
-Dosgi.nls.warnings=ignore
-Djava.class.path=C:\Users\e1032606\AppData\Local\MYECLI~2\../Temp/MyEclips.001/INSTAL~1/CONFIG~1/ORGECL~1.OSG/bundles/4/data/140498~1/plugins/OR47CC~1.JAR

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

*** Eclipse details:
MyEclipse Blue Edition

Version: 2013 SR1 Blue
Build id: 11.0.1-Blue-20130621

Blueprint: N/A

com.genuitec.eclipse.mobile.feature – 11.0.1.201306201451
com.genuitec.myeclipse.blue.feature – 11.0.1.me201306201512
com.genuitec.myeclipse.database – 11.0.1.me201306201512
com.genuitec.myeclipse.db2 – 11.0.1.me201306201512
com.genuitec.myeclipse.desktop – 11.0.1.me201306201512
com.genuitec.myeclipse.geronimo – 11.0.1.me201306201512
com.genuitec.myeclipse.glassfish – 11.0.1.me201306201512
com.genuitec.myeclipse.icefaces.feature – 11.0.1.me201306201512
com.genuitec.myeclipse.imageeditor – 11.0.1.me201306201512
com.genuitec.myeclipse.jboss – 11.0.1.me201306201512
com.genuitec.myeclipse.jetty – 11.0.1.me201306201512
com.genuitec.myeclipse.jonas – 11.0.1.me201306201512
com.genuitec.myeclipse.jrun – 11.0.1.me201306201512
com.genuitec.myeclipse.jsf – 11.0.1.me201306201512
com.genuitec.myeclipse.maven – 11.0.1.me201306201512
com.genuitec.myeclipse.oracle – 11.0.1.me201306201512
com.genuitec.myeclipse.orion – 11.0.1.me201306201512
com.genuitec.myeclipse.persistence – 11.0.1.me201306201512
com.genuitec.myeclipse.reports – 11.0.1.me201306201512
com.genuitec.myeclipse.resin – 11.0.1.me201306201512
com.genuitec.myeclipse.struts – 11.0.1.me201306201512
com.genuitec.myeclipse.sun – 11.0.1.me201306201512
com.genuitec.myeclipse.tomcat – 11.0.1.me201306201512
com.genuitec.myeclipse.uml2 – 11.0.1.me201306201512
com.genuitec.myeclipse.visualvm – 11.0.1.me201306201512
com.genuitec.myeclipse.visualvm.server – 11.0.1.me201306201512
com.genuitec.myeclipse.weblogic – 11.0.1.me201306201512
com.genuitec.myeclipse.ws – 11.0.1.me201306201512
com.genuitec.myeclipse.ws.blue – 11.0.1.me201306201512
org.eclipse.birt – 4.2.1.me201306201512
org.eclipse.datatools.connectivity.feature – 1.10.1.me201306201512
org.eclipse.datatools.enablement.feature – 1.10.1.me201306201512
org.eclipse.datatools.modelbase.feature – 1.10.1.v201208161415-7707FCcNBHLCgLUEdUb
org.eclipse.datatools.sqldevtools.feature – 1.10.1.me201306201512
org.eclipse.emf – 2.8.1.v20120917-0436
org.eclipse.gef – 3.8.1.201208200205
org.eclipse.graphiti.feature – 0.9.2.v20130211-0913
org.eclipse.jpt.jpa.feature – 3.2.1.me201306201512
org.eclipse.jpt.jpadiagrameditor.feature – 1.1.1.me201306201512
org.eclipse.jst.common.fproj.enablement.jdt – 3.4.0.me201306201512
org.eclipse.jst.enterprise_ui.feature – 3.4.0.me201306201512
org.eclipse.jst.server_adapters.ext.feature – 3.3.101.me201306201512
org.eclipse.jst.server_adapters.feature – 3.2.200.me201306201512
org.eclipse.jst.server_ui.feature – 3.4.0.me201306201512
org.eclipse.jst.ws.axis2tools.feature – 1.1.200.me201306201512
org.eclipse.m2e.feature – 1.2.0.me201306201512
org.eclipse.sapphire.platform – 0.3.0.201106221325
org.eclipse.wst.common.fproj – 3.4.0.me201306201512
org.eclipse.wst.server_adapters.feature – 3.2.201.me201306201512
org.eclipse.xsd – 2.8.0.v20120917-0436
org.springframework.ide.eclipse.feature – 2.9.1.me201306201512

fr.obeo.acceleo.bridge.feature – 2.6.0.me201306201512
org.eclipse.cvs – 1.3.201.v20130116-085741-7B79FJKAkF7BG7NGE4IAJT
org.eclipse.draw2d – 3.8.1.201208200205
org.eclipse.epp.mpc – 1.1.1.I20110907-0947
org.eclipse.equinox.p2.core.feature – 1.1.0.v20121211-153934-8297FndFWmE7h7Bpz-vcqkxyKz0
org.eclipse.equinox.p2.discovery.feature – 1.0.100.v20120524-0542-4-Bh9oB58B5W8E28KKNEK
org.eclipse.equinox.p2.extras.feature – 1.1.0.v20121211-153934-7A6FEcDiVOTg2RYDuZuFz-L2z00w
org.eclipse.equinox.p2.rcp.feature – 1.1.0.v20121211-153934-785EoBqNKNZz-DW7sUc8hFwz00wd
org.eclipse.equinox.p2.user.ui – 2.2.0.v20121212-204731-62DG9JXTlTj-UXcQ2y3NLn6U4Z3H
org.eclipse.help – 1.4.1.v20120912-145617-8R7xFOXFLWUl7PpMEeZNIGkb4
org.eclipse.jdt – 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRttdWQJ-2z-_83
org.eclipse.jsf.feature – 3.4.1.me201306201512
org.eclipse.ocl – 3.1.0.v20110606-1427
org.eclipse.pde – 3.8.2.v20130116-091538-7c7wFj0FFt6Zr9bc77L7JFNNa
org.eclipse.platform – 3.8.1.v20130118-180812-9jF7oIBFG8eU2pim-VbIlTuQjY0RWWK3x-bv4I
org.eclipse.rcp – 3.8.2.v20130118-180157-96BuGOZFxwOAeG8Ofmqicz0tPK
org.eclipse.wb.core.feature – 1.5.0.r38x201206111201
org.eclipse.wb.core.ui.feature – 1.5.0.r38x201206111213
org.eclipse.wb.core.xml.feature – 1.5.0.r38x201206111216
org.eclipse.wb.doc.user.feature – 1.5.0.r38x201206111211
org.eclipse.wb.layout.group.feature – 1.5.0.r38x201206111249
org.eclipse.wb.rcp.SWT_AWT_support – 1.5.0.r38x201206111333
org.eclipse.wb.rcp.doc.user.feature – 1.5.0.r38x201206111236
org.eclipse.wb.rcp.feature – 1.5.0.r38x201206111317
org.eclipse.wb.swing.doc.user.feature – 1.5.0.r38x201206111240
org.eclipse.wb.swing.feature – 1.5.0.r38x201206111310
org.eclipse.wb.swt.feature – 1.5.0.r38x201206111304
org.eclipse.wb.xwt.feature – 1.5.0.r38x201206111323
org.sonatype.m2e.mavenarchiver.feature – 0.15.0.201207090125

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Users\e1032606\AppData\Local\MyEclipse Blue\myeclipse-blue.exe
-name
Myeclipse-blue
–launcher.library
C:\Users\e1032606\AppData\Local\MyEclipse Blue\../Temp/MyEclips.001/installer/configuration/org.eclipse.osgi/bundles/4/data/1404980637/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_3.2.0.v201103301700\eclipse_3215.dll
-startup
C:\Users\e1032606\AppData\Local\MyEclipse Blue\../Temp/MyEclips.001/installer/configuration/org.eclipse.osgi/bundles/4/data/1404980637/plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
-install
C:\Users\e1032606\AppData\Local\MyEclipse Blue
-configuration
C:\Users\e1032606\AppData\Local\MyEclipse Blue\configuration
-vm
C:\Users\e1032606\AppData\Local\Temp\MyEclips.001\installer\configuration\org.eclipse.osgi\bundles\data04980637\binary\com.sun.java.jdk.win32.x86_1.6.0.u43\jre\bin\client\jvm.dll

[support-swapna]

Jackson,

Sorry that you are seeing this issue.

Can you please take a look at this FAQ about memory issues and see if the suggested memory settings work for you?
https://www.genuitec.com/forums/topic/troubleshooting-memory-amp-performance-issues/

You could try increasing your heap beyond 768m and see if that improves the performance.

If you are still seeing issues, please switch to a new workspace, replicate the issue and copy paste the contents of the .log file which is located at <workspace dir>/.metadata/.log to help us investigate further. Also let us know if you have any third party plugins installed.

Let us know how it works for you.

[BethJackson14]

-clean
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
–launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20120522-1813
-product
org.eclipse.epp.package.jee.product
–launcher.defaultAction
openFile
–launcher.XXMaxPermSize384M
-showsplash
org.eclipse.platform
–launcher.XXMaxPermSize384m
–launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Dhelp.lucene.tokenizer=standard
-Xms40m
-Xmx768m

[support-swapna]

BethJackson14,

Apologies for the late response. Somehow I lost the notification on your reply.

Do you have any third party plugins installed?
Can you please switch to a new workspace, replicate the issue and share the contents of the .log file to help us investigate further?

We have released MyEclipse Blue 2013 SR2 recently. Can you please update to SR2 and see if the issue persists ?

[support-swapna]

BethJackson14,

I am afraid the .ini file you shared with us has errors in it.–launcher.XXMaxPermSize384m
–launcher.defaultAction are duplicated.

Can you please let us know how you have installed MyEclipse Blue 2013 ?
If you have installed MyEclipse Blue using the Installer, then please use the .ini file provided by the installer. You can edit this ini file and alter the memory settings as suggested in my previous reply.

[BethJackson14]

Please tell me what I need to change I thought I did it.
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
–launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20120522-1813
-product
org.eclipse.epp.package.jee.product
–launcher.defaultAction
openFile
–launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
–launcher.XXMaxPermSize
256m
–launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Dhelp.lucene.tokenizer=standard
-Xms40m
-Xmx512m

[support-swapna]

BethJackson14,

In your .ini file I see duplication of

–launcher.defaultAction
openFile
–launcher.XXMaxPermSize
256M

Please try with the modified .ini contents as below :

-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
–launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20120522-1813
-product
org.eclipse.epp.package.jee.product
-showsplash
org.eclipse.platform
–launcher.XXMaxPermSize
384m
–launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Dhelp.lucene.tokenizer=standard
-Xms40m
-Xmx768m

You could try increasing your heap beyond 768m and see if that improves the performance. If you are still seeing issues, please give us some more details to help us investigate further.

1. Please switch to a new workspace, replicate the issue and copy paste the contents of the .log file which is located at <workspace dir>/.metadata/.log.
2. Also please let us know how you have installed MyEclipse. This will help us investigate about the discrepancies in your .ini file

Let us know how it works for you.

[BethJackson14]

I tried your INI file but it is worse then ever. I had to cancel out it hung so long. Then I bring it back up and it haning just searching for a jsp.

The logs are empty that you point me too.

I downloaded the installation file from your website and installed on PC the way the software recommended.

Very Frustrated!

[support-tony]

Beth,

Sorry you are having troubles. The ini file we provided was modified to try to fit with ini file you posted. However, it is quite different from the ini file that is installed with the product. Also, your installation summary details indicate a 32 bit installation but your ini file specifies a 64 bit launcher library.

The ini file as installed (for a 32 bit installation of release 2013 SR2) should look something like this:

#utf8 (do not remove)
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_3.2.0.v201103301700
-vm
C:\Development\MyEclipse\SR2\Blue32\binary\com.sun.java.jdk.win32.x86_1.6.0.u43\jre\bin\client\jvm.dll
-configuration
C:\Development\MyEclipse\SR2\Blue32\configuration
-install
C:\Development\MyEclipse\SR2\Blue32
-vmargs
-Xmx512m
-XX:MaxPermSize=256m
-XX:ReservedCodeCacheSize=64m
-Dosgi.nls.warnings=ignore

Where the file paths will be different for you, depending on where you installed it. You can change the -Xmx parameter to “-Xmx768m” and the -XX:MaxPermSize parameter to “-XX:MaxPermSize=384m” though both of those values can be increased if you still have problems.

If you install the 64 bit version (the installation lets you choose 32 bit or 64 bit, if your machine supports 64 bit), then the ini file will look similar:

#utf8 (do not remove)
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_64_3.2.0.v201103301700
-vm
C:\Development\MyEclipse\SR2\Blue64\binary\com.sun.java.jdk.win32.x86_64_1.6.0.u43\bin\javaw.exe
-configuration
C:\Development\MyEclipse\SR2\Blue64\configuration
-install
C:\Users\Tony\AppData\Local\MyEclipse Blue 2013 SR2 64
-vmargs
-Xmx512m
-XX:MaxPermSize=256m
-XX:ReservedCodeCacheSize=64m
-Dosgi.nls.warnings=ignore

Note the 64 bit launcher library and the 64 bit Java VM.

Could you please try either re-installing, then altering the memory settings in the ini file, or just try the appropriate ini file contents as above (with alterations for your installation folder and memory settings)? Uninstalling and re-installing would be the recommended option since it looks like your installation may have been corrupted in some way. Remember that you can alter the memory settings after a re-install.

Please let us know how you get on.

[BethJackson14]

Here is the eclipse.ini file I am now using and attached is the log from the workspace. I am still getting (NOT RESPONDING) but it seem to occur for the first hour Eclipse is up. If i leave it up it seems to perform day to day. Can you look at the log and the ini and tell me if you see anything else that doesn’t look correct?
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
–launcher.library
plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_3.2.0.v201 103301700
-vm
C:\Users\e1032606\AppData\Local\Temp\MyEclips.001\installer \configuration\org.eclipse.osgi\bundles\data04980637\binary \com.sun.java.jdk.win32.x86_1.6.0.u43\jre\bin\client\jvm.dll
-configuration
C:\eclipse\configuration
-install
C:\eclipse
-vmargs
-Xmx768m
-XX:MaxPermSize=384m
-XX:ReservedCodeCacheSize=64m
-Dosgi.nls.warnings=ignore

[BethJackson14]

WHy do you think the installation is bad in your statement below – ‘Uninstalling and re-installing would be the recommended option since it looks like your installation may have been corrupted in some way. Remember that you can alter the memory settings after a re-install’

I just followed the prompts to install it. WHat indicates that would fix it?

[support-tony]

Beth,

I don’t know if your installation had been corrupted but I couldn’t figure out how you could start MyEclipse Blue when it was reporting a 32 bit architecture but you were pointing to 64 bit libraries in your ini file.

To be honest, I’m still confused. You call the ini file “eclipse.ini”. Do you mean “myeclipse-blue.ini”? The ini file needs to be the same name as the exe file used to launch MyEclipse Blue (“myeclipse-blue.exe”). However, parts of the ini file you posted seem to suggest that you have installed MyEclipse Blue on top of an eclipse install (the line after -install shows “C:\eclipse”). However, the -vm specified is from a temp directory that looks like it might be from a MyEclipse Blue install. As posted, the ini file appears to also have spurious space (in the launcher.library path and the vm path) but this might just be copy and paste issues. So, the ini file is confusing me.

So, some questions to see if I can understand your situation.

1. You said you installed from the installer that you downloaded from our Web site. Did you just accept all of the defaults? Which folder did you install into?
2. As you don’t appear to have used the ini file (myeclipse-blue.ini) that is produced by the installer, what is the reasoning behind the changes you’ve made, just so I understand what you’re trying to achieve.
3. Can you please try uninstalling MyEclipse Blue then reinstalling (in whichever folder you like) and then launching the IDE as installed, just to see if that makes a difference for you. If it works, then just alter the memory parameters in the “myeclipse-blue.ini” file and see if that works fine for you.
4. If you still see the “Not Responding” message, is it intermittent, or does it stop you from working with the IDE at all, for an hour?
5. If you continue having issues please attach the .log file in the .metadata folder of the workspace (you may need to rename it to be able to attach it). Also, let us know if there is any task showing in the status message at the bottom right of the MyEclipse main window, when the “Not Responding” text shows in the window title.

Some tips for improved startup and general performance:

• A few users have had trouble with the project migration scanner taking up too much processor time. This is a task which looks for old projects that need to be migrated to work better with the latest release of MyEclipse. If you see a message about scanning for projects to migrate, often, you can disable the scan by going to MyEclipse->Preferences->MyEclipse->Project Migration and select the disable checkbox.
• The maven feature updates the maven catalog index at start up. This runs in the background to enable quick use of some maven functionality. However, it can also be turned off in the MyEclipse preferences by going to the Maven4MyEclipse page and unchecking the “Download repository index updates on startup” option.

Please get back to us with the answers to the questions and let us know how you get on with the suggestions.

[Author]

Posts