[Knut Erik Ballestad]

I get this error when rebuilding a Struts+Hibernate project:

!ENTRY org.eclipse.osgi aug 12, 2004 08:15:55.321
!MESSAGE While loading class "com.genuitec.eclipse.ast.deploy.core.ui.action.DeploymentMgmtActionDelegate", thread "main" timed out waiting (5000ms) for thread "Thread-0" to finish starting bundle "com.genuitec.eclipse.ast.deploy.core". To avoid deadlock, thread "main" is proceeding but "com.genuitec.eclipse.ast.deploy.core.ui.action.DeploymentMgmtActionDelegate" 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(Unknown Source)
    at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:307)
    at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:336)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1313)
    at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:131)
    at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:124)
    at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:113)
    at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:189)
    at org.eclipse.ui.internal.PluginAction.createDelegate(PluginAction.java:114)
    at org.eclipse.ui.internal.WWinPluginAction.refreshActionList(WWinPluginAction.java:147)
    at org.eclipse.ui.plugin.AbstractUIPlugin$3.run(AbstractUIPlugin.java:803)
    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(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    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)

!ENTRY org.eclipse.ui 4 4 aug 12, 2004 13:08:19.60
!MESSAGE Unhandled event loop exception

[Knut Erik Ballestad]

The exception is then followed by lots of these:

!ENTRY org.eclipse.ui 4 0 aug 12, 2004 13:08:20.112
!MESSAGE java.lang.OutOfMemoryError
!STACK 0
java.lang.OutOfMemoryError
!SESSION aug 12, 2004 14:00:43.802 ---------------------------------------------
eclipse.buildId=I200406251208
java.version=1.4.2_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=no_NO

!ENTRY de.bb.bje.eclipse 4 1 aug 12, 2004 14:00:50.112
!MESSAGE JSP Compiler broken
!STACK 0
java.lang.OutOfMemoryError

!ENTRY de.bb.bje.eclipse 4 1 aug 12, 2004 14:01:12.94
!MESSAGE JSP Compiler broken
!STACK 0
java.lang.OutOfMemoryError

!ENTRY org.eclipse.ui 4 4 aug 12, 2004 14:01:30.391
!MESSAGE Unhandled event loop exception

!ENTRY de.bb.bje.eclipse 4 1 aug 12, 2004 14:01:38.894
!MESSAGE JSP Compiler broken
!STACK 0
java.lang.OutOfMemoryError

[Scott Anderson]

keb,

You may actually be running out of memory, thus causing odd behavior. Can you try modifying your Eclipse start alias to include some
commandline args to increase memory size? Something like -vm -Xms128M -Xmx256M should do it. Eclipse 3.0 uses quite a bit more ram than 2.1 did.

If that doesn’t do it, can you please post all the information we request in the [URL=http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-393.html]Posting Guidelines[/URL] thread at the top of this forum? That will give us some context so that we can determine if this is an installation issue, a configuration problem, or a bug. Thanks.

[Knut Erik Ballestad]

@support-scott wrote:

keb,
You may actually be running out of memory, thus causing odd behavior. Can you try modifying your Eclipse start alias to include some
commandline args to increase memory size? Something like -vm -Xms128M -Xmx256M should do it. Eclipse 3.0 uses quite a bit more ram than 2.1 did.

I use these settings:
-vmargs -Xms256m -Xmx512m

@support-scott wrote:

If that doesn’t do it, can you please post all the information we request in the [URL=http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-393.html]Posting Guidelines[/URL] thread at the top of this forum? That will give us some context so that we can determine if this is an installation issue, a configuration problem, or a bug. Thanks.

I run on:
– Win XP SP2
– Eclipse 3.0 freshly installed for ME3.8B2
– No other plugins installed, 8 org.eclipse.pde directories
– JDK 1.4.2_03 is used to launch both Eclipse and JBoss 3.2.5
– I increased the compiler warning levels, an d then this happened – seems to have gone away when decreasing the compiler warning levels again.

[Scott Anderson]

– I increased the compiler warning levels, an d then this happened – seems to have gone away when decreasing the compiler warning levels again.

Now that’s really peculiar. And it’s consistent that you have problems with the warning levels increased, but not when they’re set to the default?

In any case, most of the places this could occur have been reworked a bit for 3.8 GA and that build should be available later today. When you get the GA build installed, please let us know if this problem is reproducable with it and we’ll investigate further.

[Author]

Posts