[Riyad Kalla]

I’d appreciate any help narrowing this down, but I’ve just encountered this bug 3 times in the last 30 minutes and it seems to be directly tied to starting/stopping the Tomcat 5.0.16 server.

I have been coding and working on my project for about 2 hrs with a fresh load of Eclipse. I started up Tomcat to see if my changes were working, played around on the website I’m working on for about 3 minutes, alt-tabbed back to Eclipse, and then after clicking on anything I get the “A memory exception has occured, its suggested that you close the workbench and restart” dialog popping up. So i can’t work because it just keeps popping up after clicking on anything.

But that’s not the worst part… I then close down eclipse, which exists gracefully. Now when I try and load eclipse (the 1st time after that problem) I get an error dialog popping up saying that eclispe was unable to start and I should check the log file. After checking the log file, I have this:

these are my last 4 sessions from the log file

!SESSION ----------------------------------------------------------------------
!ENTRY org.eclipse.core.launcher 4 0 Jan 06, 2004 13:51:46.849
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.reflect.InvocationTargetException
    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:291)
    at org.eclipse.core.launcher.Main.run(Main.java:747)
    at org.eclipse.core.launcher.Main.main(Main.java:583)
Caused by: java.lang.reflect.InvocationTargetException
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:861)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    ... 7 more
Caused by: java.lang.OutOfMemoryError

!SESSION ----------------------------------------------------------------------
!ENTRY org.eclipse.core.launcher 4 0 Jan 06, 2004 13:52:57.58
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.reflect.InvocationTargetException
    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:291)
    at org.eclipse.core.launcher.Main.run(Main.java:747)
    at org.eclipse.core.launcher.Main.main(Main.java:583)
Caused by: java.lang.reflect.InvocationTargetException
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:861)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    ... 7 more
Caused by: java.lang.OutOfMemoryError

!SESSION Jan 06, 2004 14:30:03.972 ---------------------------------------------
java.version=1.4.2_02
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86 -install file:/home/rkalla/java/eclipse/
!ENTRY org.eclipse.ui 4 4 Jan 06, 2004 14:30:03.973
!MESSAGE Unhandled exception caught in event loop.
!ENTRY org.eclipse.ui 4 0 Jan 06, 2004 14:30:03.974
!MESSAGE java.lang.OutOfMemoryError
!STACK 0
java.lang.OutOfMemoryError
!ENTRY org.eclipse.ui 4 4 Jan 06, 2004 14:30:11.759
!MESSAGE Unhandled exception caught in event loop.
!ENTRY org.eclipse.ui 4 0 Jan 06, 2004 14:30:11.759
!MESSAGE java.lang.OutOfMemoryError
!STACK 0
java.lang.OutOfMemoryError
!ENTRY org.eclipse.ui 4 4 Jan 06, 2004 14:30:31.478
!MESSAGE Unhandled exception caught in event loop.
!ENTRY org.eclipse.ui 4 0 Jan 06, 2004 14:30:31.479
!MESSAGE java.lang.OutOfMemoryError
!STACK 0
java.lang.OutOfMemoryError
!SESSION ----------------------------------------------------------------------
!ENTRY org.eclipse.core.launcher 4 0 Jan 06, 2004 14:31:05.75
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.reflect.InvocationTargetException
    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:291)
    at org.eclipse.core.launcher.Main.run(Main.java:747)
    at org.eclipse.core.launcher.Main.main(Main.java:583)
Caused by: java.lang.reflect.InvocationTargetException
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:861)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    ... 7 more
Caused by: java.lang.OutOfMemoryError

So this doesn’t really help me, so I hit OK, get rid of the dialog and try eclipse again, now what happens is that I get the splash screen to show up and perpetually sit there. Nothing is written to the log file, nothing happens with the eclipse process or any of its child java processes, no activity, nada…

The only solution I’ve found is to close KDE, do a skill -9 <user name> at my console and log back in, load KDE back up and reload Eclipse, then it works.

Note: I’ve tried ps ax and top to see if there are ANY stray java, eclipse, or java-related processes running around and there aren’t. But for some reason existing and logging out of my account is the only thing that lets Eclipse load after this problem (maybe a file handle issue? I have no idea…)

Here are my specs:

Gentoo Linux (2.4.24 Kernel)
KDE 3.1.4
Sun JDK 1.4.2_02 (for everything)
Eclipse 2.1.2
ME 2.7RC2
(other plugins)
JFaceDBC

And I’m not using any vmargs

Anybody else experiencing any out of memory exceptions like this? The weird part is that it only pops up after starting/stopping Tomcat, not while editing or working in the workbench.

[Riyad Kalla]

more info:

This time I waited about 10 mins then tried loading eclipse again (without logging out) and it loaded up alright. I’m guessing something timed out and got released that eclipse needed to startup. I’ve also been starting/stopping tomcat and Eclipse is still working with no out of memory exceptions… strange

[Riyad Kalla]

UPDATE: I’ve been using Eclipse now for about 4 hours straight doing a bunch of Tomcat/JSP work and had no problems… and the OOM exception just occured again. I can’t seem to narrow down what the problem is, but it happened when I went to do a CVS operation.

Also it seems saving a file doesn’t compile it anymore (.java source file), I’m not sure why. This doesn’t work any longer in my Java or MyEclipse perspectives.

[Riyad Kalla]

DETAIL: Every time I try and start Eclipse I get this exception:

!SESSION ----------------------------------------------------------------------
!ENTRY org.eclipse.core.launcher 4 0 Jan 06, 2004 17:18:29.750
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.reflect.InvocationTargetException
    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:291)
    at org.eclipse.core.launcher.Main.run(Main.java:747)
    at org.eclipse.core.launcher.Main.main(Main.java:583)
Caused by: java.lang.reflect.InvocationTargetException
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:861)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    ... 7 more
Caused by: java.lang.OutOfMemoryError

[Riyad Kalla]

UPDATE: In an effort to get back to work I kept erasing and replacing files in my workspace dir to see which one had become corrupt, and it seems the:
<userdir>/workspace/.metadata/.keyring

file was the culprit. I erased this and Eclipse came right up. I lost my CVS passwords but that wasn’t too bad. This is strange as I mentioned I was performing a CVS operation when Eclipse threw the OOM exception, and I’m wondering if the keyring file is the cvspasswd file, in which case Eclipse, not ME, is corrupting itself.

Thoughts?

[Author]

Posts