facebook

Hard Eclipse crash (VM crash) when trying to open JSP

  1. MyEclipse Archived
  2.  > 
  3. Bugs
Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #219833 Reply

    Eric Rizzo
    Member

    I’m getting very hard Eclipse crashes (the old “JVM terminated” error dialog) when trying to open a JSP that was created with the MyEclipse Struts 1.1 JSP template. I fact, I can’t even keep my Eclipse workbench running for very long since this file was created in my workspace.
    The workbench comes up and by enabling verbose mode on the progress view I can watch what it is trying to do. When the Building Workspace task gets to this JSP file, it crashes Eclipse, VM and all.
    I can at least keep my workbench up for a while if I cancel the Building Workspace task in Progress view, but as soon as I do anything that tries to build the project that JSP is in, it crashes again.
    I emptied my workspace .log file before trying to edit the JSP, let it crash, then looked in the .log – it is empty.

    In general, I’ve been experiencing 1 or 2 Eclipse crashes per day ever since installing My Eclipse, even before trying to create/edit this JSP. Before that I had perhaps 1 or 2 crashes in Eclipse 3.0 total in 6 months (no VM/JDK or Eclipse version changes in that time). And again, I reiterate, there is nothing in this particularly problematic JSP file except what MyEclipse template put in there.

    So what info can I gather and provide that will help to track down the cause ASAP? Here is the details about Eclipse/MyEclipse and my system:
    Windows XP
    Eclipse 3.0.0 running under JDK 1.4.2_04
    MyEclipse 3.8.2

    Also, am I better off contacting support directly about this, as opposed to using these forums?

    Eric

    #219834 Reply

    Riyad Kalla
    Member

    Eric,
    First lets try and apply this quickfix here:
    http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-4498.html

    Second lets make sure you are giving Eclipse enough Memory to run:

    
    eclipse.exe -vmargs -Xms128m -Xmx256m
    

    MyEclipse is a huge piece of software, so ontop of Eclipse 3 it does require more memory than the default 64mb heap that is given to the VM.

    #219835 Reply

    Eric Rizzo
    Member

    @support-rkalla wrote:

    Eric,
    First lets try and apply this quickfix here:
    http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-4498.html

    Second lets make sure you are giving Eclipse enough Memory to run:

    
    eclipse.exe -vmargs -Xms128m -Xmx256m
    

    MyEclipse is a huge piece of software, so ontop of Eclipse 3 it does require more memory than the default 64mb heap that is given to the VM.

    I’ll give the QuickFix a try and report the results.
    I already give Eclipse extra heap to run in (256MB).

    #219837 Reply

    Eric Rizzo
    Member

    @support-rkalla wrote:

    Eric,
    First lets try and apply this quickfix here:
    http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-4498.html

    Installed and confirmed the QuickFix. It seems to have helped some. Eclipse still crashed when I first created a new JSP from the “Struts 1.1 with Form Bean” template. But it no longer crashes when I restarted Eclipse and tried editing the JSP.

    #219843 Reply

    Riyad Kalla
    Member

    What is the stack trace in the log file every time it crashes?
    <workspace dir>\.metadata\.log

    This will be critical in helping us figure out what is going on… also please give me the Build ID of Eclipse that you are using and JDK version and subversion.

    #219889 Reply

    Eric Rizzo
    Member

    As I said originally, the .log file provides nothing about this. I’ve been emptying it each time I start Eclipse and go look when it crashes. There are sometimes some minor errors that don’t seem related, but never anything from around the time that Eclipse crashes.
    This has gotten progressively worse in the past two days – it has crashed the VM 3 times since I started working this morning, only 2.5 hours ago!
    Please tell me there is some way to get more logging info out of MyEclipse and/or Eclipse platform than the default .log…

    Is there a “real” support channel I can escalate this to? It has moved beyond just problems editing a particular JSP, to the point where I can’t be productive with MyEclipse installed any more.

    #219890 Reply

    Eric Rizzo
    Member

    Here is a snapshot of my workspace .log file from the last attempt to start Eclipse with a MyEclipse project open.

    !SESSION Nov 23, 2004 09:31:55.581 ———————————————
    eclipse.buildId=I200406251208
    java.version=1.4.2_04
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

    !ENTRY org.eclipse.update.configurator Nov 23, 2004 09:31:55.597
    !MESSAGE Could not install bundle /c:/Java/eclipse/3.0/plugins/org.eclipse.draw2d_3.0.0/ Bundle “org.eclipse.draw2d” version “3.0.0” has already been installed from: update@/C:/Java/eclipse/MyEclipseEnterpriseWorkbench/eclipse/plugins/org.eclipse.draw2d_3.0.0/

    !ENTRY org.eclipse.update.configurator Nov 23, 2004 09:31:55.690
    !MESSAGE Could not install bundle /c:/Java/eclipse/3.0/plugins/org.eclipse.gef_3.0.0/ Bundle “org.eclipse.gef” version “3.0.0” has already been installed from: update@/C:/Java/eclipse/MyEclipseEnterpriseWorkbench/eclipse/plugins/org.eclipse.gef_3.0.0/

    !ENTRY org.eclipse.ui 4 4 Nov 23, 2004 09:32:41.143
    !MESSAGE Category Other not found for view ganymede.views.GanymedeView. This view added to ‘Other’ category.

    !ENTRY org.eclipse.osgi Nov 23, 2004 09:32:51.784
    !MESSAGE While loading class “org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument$ConsoleLine”, thread “main” timed out waiting (5000ms) for thread “Worker-2” to finish starting bundle “org.eclipse.team.cvs.ui”. To avoid deadlock, thread “main” is proceeding but “org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument$ConsoleLine” may not be fully initialized.
    !STACK 0
    java.lang.Exception: Generated exception.
    at org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(EclipseClassLoader.java:102)
    at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:371)
    at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:402)
    at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:93)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument.getLines(ConsoleDocument.java:78)
    at org.eclipse.team.internal.ccvs.ui.console.CVSOutputConsole.dump(CVSOutputConsole.java:150)
    at org.eclipse.team.internal.ccvs.ui.console.CVSOutputConsole.access$1(CVSOutputConsole.java:147)
    at org.eclipse.team.internal.ccvs.ui.console.CVSOutputConsole$1.run(CVSOutputConsole.java:118)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:106)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:2749)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2434)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1377)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:254)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
    at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:335)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:183)
    at org.eclipse.core.launcher.Main.run(Main.java:644)
    at org.eclipse.core.launcher.Main.main(Main.java:628)
    !SESSION Nov 23, 2004 11:36:42.160 ———————————————
    eclipse.buildId=I200406251208
    java.version=1.4.2_04
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

    !ENTRY org.eclipse.update.configurator Nov 23, 2004 11:36:42.160
    !MESSAGE Could not install bundle /c:/Java/eclipse/3.0/plugins/org.eclipse.draw2d_3.0.0/ Bundle “org.eclipse.draw2d” version “3.0.0” has already been installed from: update@/C:/Java/eclipse/MyEclipseEnterpriseWorkbench/eclipse/plugins/org.eclipse.draw2d_3.0.0/

    !ENTRY org.eclipse.update.configurator Nov 23, 2004 11:36:42.253
    !MESSAGE Could not install bundle /c:/Java/eclipse/3.0/plugins/org.eclipse.gef_3.0.0/ Bundle “org.eclipse.gef” version “3.0.0” has already been installed from: update@/C:/Java/eclipse/MyEclipseEnterpriseWorkbench/eclipse/plugins/org.eclipse.gef_3.0.0/

    !ENTRY org.eclipse.ui 4 4 Nov 23, 2004 11:37:52.751
    !MESSAGE Category Other not found for view ganymede.views.GanymedeView. This view added to ‘Other’ category.

    !ENTRY org.eclipse.osgi Nov 23, 2004 11:38:06.626
    !MESSAGE While loading class “org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument$ConsoleLine”, thread “main” timed out waiting (5000ms) for thread “Worker-4” to finish starting bundle “org.eclipse.team.cvs.ui”. To avoid deadlock, thread “main” is proceeding but “org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument$ConsoleLine” may not be fully initialized.
    !STACK 0
    java.lang.Exception: Generated exception.
    at org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(EclipseClassLoader.java:102)
    at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:371)
    at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:402)
    at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:93)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument.getLines(ConsoleDocument.java:78)
    at org.eclipse.team.internal.ccvs.ui.console.CVSOutputConsole.dump(CVSOutputConsole.java:150)
    at org.eclipse.team.internal.ccvs.ui.console.CVSOutputConsole.access$1(CVSOutputConsole.java:147)
    at org.eclipse.team.internal.ccvs.ui.console.CVSOutputConsole$1.run(CVSOutputConsole.java:118)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:106)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:2749)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2434)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1377)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:254)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
    at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:335)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:183)
    at org.eclipse.core.launcher.Main.run(Main.java:644)
    at org.eclipse.core.launcher.Main.main(Main.java:628)

    #219891 Reply

    Riyad Kalla
    Member

    erizzo please provide me the Build ID of your Eclipse install that you are using (Help > About) and MyEclipse (Windows > Preferences > MyEclipse, don’t use the Help > About build ID for ME). I will send off this info for others to look at then.

    #219893 Reply

    Riyad Kalla
    Member

    erizzo,
    From that log file things look pretty mucked up… I would highly suggest you go to Eclipse’s site and grab Eclipse 3.0.1 SDK (~85mb), download it and unzip it to a new location and launch it (Create a new workspace). Then use Help > Software Updates > Manage Configs > (right click) Add > New Extension and point at your MyEclipse dit and let Eclipse restart and this time point to your old workspace… are things better? If not, try and use the new workspace and reimport your projects until things are fixed.

    You can also try restarting your current install by adding “-clean” to your command line used to start Eclipse, give it a chance to clean out the config cache, maybe something is mucking it up during startup… over all it looks like a mish mosh of plugin installs/removals are creating problems for you, so a good way to go right now is a clean reinstall. Also there were about 269 bug fixes between Eclipse 3.0 and 3.0.1, so its a nice upgrade either way.

    #219895 Reply

    Eric Rizzo
    Member

    Eclipse bulid is 200406251208 – it is the 3.0.0 Final Release
    MyEclipse is the QuickFix 2 installed yesterday, 200410041200-3.8.2+QF20041020

    (BTW, you guys should make that build number selectable so it can be copy/pasted)

    #219905 Reply

    Eric Rizzo
    Member

    Upgrading to a new build of Eclipse and re-building my entire workspace is not an option right now. I’m sure you realize that effort is not trivial because of the numerous preference items that need to be exported and re-imported, the numerous plugins that must be re-installed, launch configs that must be re-created, the large slow 80+ MB download, re-installing MyEclipse, etc. etc.
    Doing that would put me out of commission for at least a day (trust me, I’ve done that kind of install/upgrade several times before).
    To be honest, the log file is not very messy IME. There are a couple of issues relating to MyEclipse and GEF/Draw2d plugins, one plugin that has a poorly specified category for its view (not a real problem – I’ve been seeing that one for at least a year without any other symptoms), and then the mystery “timeout error.” Do you have any insight into that one, because it is the one thing that is new since I started using MyEclipse on a daily basis?
    Is there a way to uninstall MyEclipse “temporarily” so that I can experiment to see if that makes things any more stable?
    Are there any other options for enabling exended logging?

    #219916 Reply

    Riyad Kalla
    Member

    Upgrading to a new build of Eclipse and re-building my entire workspace is not an option right now.

    That’s fine, then just do all the steps I told you and point at your existing workspace OR try using -clean, these are two other options that don’t have anything to do with rebuilding your workspace.

    Is there a way to uninstall MyEclipse “temporarily” so that I can experiment to see if that makes things any more stable?

    Help > Software Updates > Manage Confing > Click on MyEclipse, click “Disable” (restart)

    Are there any other options for enabling exended logging?

    Not that I’m aware of. I will ask.

Viewing 12 posts - 1 through 12 (of 12 total)
Reply To: Hard Eclipse crash (VM crash) when trying to open JSP

You must be logged in to post in the forum log in