[David Beckedorff]

XDoclet generation under ME ran out of memory. Not sure why, since I have only 6 session beans and 512MB of memory on my machine. I am now unable to restart the Eclipse UI.

Looking for suggestions on how to (1) recover the IDE and (2) prevent a re-occurrence of this sort of crash.

My env: Win XP, Eclipse 2.1.2, ME-2.7.0GA (installed today via Eclipse Update Manager), JDK 1.4.2_03.

Eclipse log file:

!ENTRY com.genuitec.jboss.ide.eclipse.xdoclet.ui 4 0 Mar 10, 2004 16:21:56.591
!MESSAGE Error while running XDoclet
!STACK 1
org.eclipse.core.runtime.CoreException[1]: file:C:/Eclipse/eclipse-2.1.2/data/XFVMEJB/xdoclet-build.xml:48: null
at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:103)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:569)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:367)
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.ant.core.AntRunner.run(AntRunner.java:335)
at org.eclipse.ui.externaltools.internal.ant.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:189)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:156)
at org.jboss.ide.eclipse.xdoclet.run.ui.actions.XDocletRunAction$1.run(XDocletRunAction.java:151)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
Caused by: java.lang.OutOfMemoryError
— Nested Exception —
java.lang.OutOfMemoryError
!ENTRY org.eclipse.ant.core 4 1 Mar 10, 2004 16:21:56.601
!MESSAGE file:C:/Eclipse/eclipse-2.1.2/data/XFVMEJB/xdoclet-build.xml:48: null
!STACK 0
file:C:/Eclipse/eclipse-2.1.2/data/XFVMEJB/xdoclet-build.xml:48: null
at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:103)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:569)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:367)
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.ant.core.AntRunner.run(AntRunner.java:335)
at org.eclipse.ui.externaltools.internal.ant.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:189)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:156)
at org.jboss.ide.eclipse.xdoclet.run.ui.actions.XDocletRunAction$1.run(XDocletRunAction.java:151)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
Caused by: java.lang.OutOfMemoryError
— Nested Exception —
java.lang.OutOfMemoryError
!SESSION Mar 10, 2004 16:22:26.755 ———————————————
java.version=1.4.2_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -data C:\Eclipse\eclipse-2.1.2\data -install file:C:/Eclipse/eclipse-2.1.2/eclipse/
!ENTRY org.eclipse.ui 4 4 Mar 10, 2004 16:22:26.755
!MESSAGE Unable to find element factory: org.eclipse.ui.internal.model.ResourceFactory
!ENTRY org.eclipse.ui 4 4 Mar 10, 2004 16:22:26.755
!MESSAGE Unable to restore pagee – cannot instantiate input factory: org.eclipse.ui.internal.model.ResourceFactory
!ENTRY org.eclipse.ui 4 4 Mar 10, 2004 16:22:26.856
!MESSAGE Unable to create default perspective – constructor failed.
!ENTRY org.eclipse.ui.workbench 4 2 Mar 10, 2004 16:22:26.856
!MESSAGE Problems occurred when invoking code from plug-in: “org.eclipse.ui.workbench”.
!STACK 0
java.lang.NullPointerException
at org.eclipse.ui.internal.WorkbenchWindow.restoreState(WorkbenchWindow.java:1364)
at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1263)
at org.eclipse.ui.internal.Workbench.access$10(Workbench.java:1223)
at org.eclipse.ui.internal.Workbench$12.run(Workbench.java:1141)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
at org.eclipse.core.runtime.Platform.run(Platform.java:413)
at org.eclipse.ui.internal.Workbench.openPreviousWorkbenchState(Workbench.java:1093)
at org.eclipse.ui.internal.Workbench.init(Workbench.java:870)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1373)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
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)
!ENTRY org.eclipse.core.resources 2 1 Mar 10, 2004 16:22:34.277
!MESSAGE Skipping builder org.eclipse.ui.externaltools.ExternalToolBuilder for project XFVMEJB. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.
!SESSION Mar 10, 2004 16:22:59.704 ———————————————
java.version=1.4.2_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -data C:\Eclipse\eclipse-2.1.2\data -install file:C:/Eclipse/eclipse-2.1.2/eclipse/
!ENTRY org.eclipse.ui 4 4 Mar 10, 2004 16:22:59.714
!MESSAGE Unable to create default perspective – constructor failed.
!ENTRY org.eclipse.ui.workbench 4 2 Mar 10, 2004 16:22:59.724
!MESSAGE Problems occurred when invoking code from plug-in: “org.eclipse.ui.workbench”.
!STACK 0
java.lang.NullPointerException
at org.eclipse.ui.internal.WorkbenchWindow.restoreState(WorkbenchWindow.java:1364)
at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1263)
at org.eclipse.ui.internal.Workbench.access$10(Workbench.java:1223)
at org.eclipse.ui.internal.Workbench$12.run(Workbench.java:1141)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
at org.eclipse.core.runtime.Platform.run(Platform.java:413)
at org.eclipse.ui.internal.Workbench.openPreviousWorkbenchState(Workbench.java:1093)
at org.eclipse.ui.internal.Workbench.init(Workbench.java:870)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1373)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
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)
!ENTRY org.eclipse.core.resources 2 1 Mar 10, 2004 16:23:10.360
!MESSAGE Skipping builder org.antlr.eclipse.core.antlrbuilder for project EZM. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.
!ENTRY org.eclipse.core.resources 2 1 Mar 10, 2004 16:23:10.370
!MESSAGE Skipping builder org.eclipse.jdt.core.javabuilder for project EZM. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.
!ENTRY org.eclipse.core.resources 2 1 Mar 10, 2004 16:23:10.380
!MESSAGE Skipping builder org.eclipse.ui.externaltools.ExternalToolBuilder for project XFVMEJB. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.
!ENTRY org.eclipse.core.resources 2 1 Mar 10, 2004 16:23:10.380
!MESSAGE Skipping builder org.eclipse.jdt.core.javabuilder for project XFVMEJB. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.
!ENTRY org.eclipse.core.resources 2 1 Mar 10, 2004 16:23:11.261
!MESSAGE Skipping builder com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder for project XFVMEJB. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.
!ENTRY org.eclipse.core.resources 2 1 Mar 10, 2004 16:23:11.271
!MESSAGE Skipping builder org.eclipse.jdt.core.javabuilder for project XFVMWeb. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.
!ENTRY org.eclipse.core.resources 2 1 Mar 10, 2004 16:23:11.271
!MESSAGE Skipping builder de.bb.bje.eclipse.IncrementalJspBuilder for project XFVMWeb. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.
!ENTRY org.eclipse.core.resources 2 1 Mar 10, 2004 16:23:11.271
!MESSAGE Skipping builder com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder for project XFVMWeb. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.
!ENTRY org.eclipse.core.resources 2 1 Mar 10, 2004 16:23:11.281
!MESSAGE Skipping builder com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder for project XFVM. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.

XDoclet build file:

<?xml version=”1.0″ encoding=”UTF-8″?>

<project default=”_generation_” name=”XDoclet Generator”>

<path id=”xdoclet.classpath”>
<pathelement location=”C:/Eclipse/eclipse-2.1.2/data/XFVMEJB/classes”/>
<pathelement location=”C:/j2sdk1.4.2_03/jre/lib/rt.jar”/>
<pathelement location=”C:/j2sdk1.4.2_03/jre/lib/sunrsasign.jar”/>
<pathelement location=”C:/j2sdk1.4.2_03/jre/lib/jsse.jar”/>
<pathelement location=”C:/j2sdk1.4.2_03/jre/lib/jce.jar”/>
<pathelement location=”C:/j2sdk1.4.2_03/jre/lib/charsets.jar”/>
<pathelement location=”C:/j2sdk1.4.2_03/jre/lib/ext/dnsns.jar”/>
<pathelement location=”C:/j2sdk1.4.2_03/jre/lib/ext/ldapsec.jar”/>
<pathelement location=”C:/j2sdk1.4.2_03/jre/lib/ext/localedata.jar”/>
<pathelement location=”C:/j2sdk1.4.2_03/jre/lib/ext/sunjce_provider.jar”/>
<pathelement location=”C:/Tools/xerces-2_6_1/xercesImpl.jar”/>
<pathelement location=”C:/Programs/MyEclipse/me-2.7/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_2.6.200/data/libraryset/1.3/activation.jar”/>
<pathelement location=”C:/Programs/MyEclipse/me-2.7/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_2.6.200/data/libraryset/1.3/javax.servlet.jar”/>
<pathelement location=”C:/Programs/MyEclipse/me-2.7/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_2.6.200/data/libraryset/1.3/jboss-j2ee.jar”/>
<pathelement location=”C:/Programs/MyEclipse/me-2.7/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_2.6.200/data/libraryset/1.3/jboss-jaas.jar”/>
<pathelement location=”C:/Programs/MyEclipse/me-2.7/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_2.6.200/data/libraryset/1.3/jsse.jar”/>
<pathelement location=”C:/Programs/MyEclipse/me-2.7/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_2.6.200/data/libraryset/1.3/jts.jar”/>
<pathelement location=”C:/Programs/MyEclipse/me-2.7/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_2.6.200/data/libraryset/1.3/mail.jar”/>
<pathelement location=”C:/Tools/jakarta-log4j-1.2.8/dist/lib/log4j-1.2.8.jar”/>
<pathelement location=”C:/Tools/axis-1_1/lib/axis.jar”/>
<pathelement location=”C:/Tools/axis-1_1/lib/axis-ant.jar”/>
<pathelement location=”C:/Tools/axis-1_1/lib/commons-discovery.jar”/>
<pathelement location=”C:/Tools/axis-1_1/lib/commons-logging.jar”/>
<pathelement location=”C:/Tools/axis-1_1/lib/jaxrpc.jar”/>
<pathelement location=”C:/Tools/axis-1_1/lib/saaj.jar”/>
<pathelement location=”C:/Tools/axis-1_1/lib/wsdl4j.jar”/>
<pathelement location=”C:/Database/JDBC/Oracle/ojdbc14.jar”/>
<pathelement location=”C:/Database/JDBC/SQLServer/msutil.jar”/>
<pathelement location=”C:/Database/JDBC/SQLServer/msbase.jar”/>
<pathelement location=”C:/Database/JDBC/SQLServer/mssqlserver.jar”/>

<fileset dir=”C:/Programs/MyEclipse/me-2.7/eclipse/plugins/org.jboss.ide.eclipse.xdoclet.core_2.6.200/”>
<include name=”*.jar”/>
</fileset>
</path>

<target name=”_generation_” depends=”N10004″/>

<target name=”N10004″ description=”Standard EJB”>

<taskdef classpathref=”xdoclet.classpath” classname=”xdoclet.modules.ejb.EjbDocletTask” name=”ejbdoclet”/>

<ejbdoclet ejbSpec=”2.0″ excludedTags=”@version,@author,@todo” destDir=”src” verbose=”true” addedTags=”@xdoclet-generated at ${TODAY},@copyright The XDoclet Team,@author XDoclet,@version ${version}” >

<fileset dir=”src” includes=”**/ejb/*.java” >
</fileset>

<packageSubstitution packages=”ejb” substituteWith=”interfaces” >
</packageSubstitution>

<remoteinterface>
</remoteinterface>

<localinterface>
</localinterface>

<homeinterface>
</homeinterface>

<localhomeinterface>
</localhomeinterface>

<session>
</session>

<utilobject cacheHomes=”true” includeGUID=”true” >
</utilobject>

<deploymentdescriptor validateXML=”true” destDir=”src/META-INF” >
</deploymentdescriptor>

<jboss>
</jboss>

<oc4j>
</oc4j>

<weblogic>
</weblogic>

</ejbdoclet>

</target>

</project>

[Riyad Kalla]

Ant seems to (unfortunately) create quite a problem with OutOfMemoryExceptions (especially with XDoclet). What happens when you try and restart Eclipse? I have run into a problem like this on Linux a few times, and the key for me was to remove the .metadata\plugins directory that pertained to the plugin that was throwing errors in my log file… in your case it seems to be org.eclipse.ui.workbench. So I would suggest deleting (or moving, if you want to be safe) the directory:
<eclipse install>/workspace/.metadata/.plugins/org.eclipse.ui.workbench

and see if you are able to restart Eclipse.

[David Beckedorff]

Thank you for your suggestion, Riyad. This time around, I reinstalled Eclipse and the ME plugin & imported my project, which I had saved. Next time, I’ll be a bit bolder and try out your idea.

Attended a seminar that Sherry Shavor gave on Eclipse this weekend at MIT (an GBC/ACM event). Asked her the same question. She also suggested moving all or part of the .metadata aside; she says Eclipse will rebuild the contents of .metadata as required based on a rescan of available plugins. I think moving the entire .metadata tree may be too drastic & your more focussed approach sounds like the right way to go.

Also, I may start doing a backup of.metadata prior to XDoclet-based rebuilds. 😉

-David

[Riyad Kalla]

Thank you for your suggestion, Riyad. This time around, I reinstalled Eclipse and the ME plugin & imported my project, which I had saved. Next time, I’ll be a bit bolder and try out your idea.

This is actually exactly what I did before it happened 3 times to me in 1 week, and I finally hit my tollerance limit so I dug into the log file and tried to fix the problem via less drastic means.

Also, I may start doing a backup of.metadata prior to XDoclet-based rebuilds.

Hah, I think that is a great idea.

There was another thread about OutOfMemoryExceptions after doing Ant/XDoclet builds, and I hunted down in the Eclipse database ~11 bugs related directly to this problem. While it seems the problem arises from Ant, and the fact that Eclipse 2.x runs Ant from within its own VM, it seems the Eclipse team fixed this problem in Eclipse 3.x by allowing Ant processes to be executed in an external VM process.

So hopefully when you move to Eclipse 3.x, these problems should disappear for you; unfortunately I don’t necessarily condone 3.x as a stable development environment just yet, although many in this forum probably would (YMMV as always).

[Author]

Posts