[Tom Cole]

I recently uninstalled MyEclipse 3.8.4 and deleted eclipse 3.0.1. I then downloaded the newest Eclipse 3.1 and MyEclipse 4.0M2. I unzipped eclipse, started it, then shut it down. I then installed MyEclipse. Then I started Eclipse.

Now I’m having a problem that everytime I create a JSP when the auto-complete box pops up I get an error window stating there was as SWT error and I should shut down the workspace.

The .log file then gets an entry like:

!ENTRY org.eclipse.ui 4 4 2005-08-13 16:05:50.939
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 2005-08-13 16:05:50.959
!MESSAGE No more handles
!STACK 0
org.eclipse.swt.SWTError: No more handles
    at org.eclipse.swt.SWT.error(SWT.java:2968)
    at org.eclipse.swt.SWT.error(SWT.java:2865)
    at org.eclipse.swt.SWT.error(SWT.java:2836)
    at org.eclipse.swt.widgets.Widget.error(Widget.java:395)
    at org.eclipse.swt.widgets.Control.createHandle(Control.java:482)
    at org.eclipse.swt.widgets.Composite.createHandle(Composite.java:229)
    at org.eclipse.swt.widgets.Decorations.createHandle(Decorations.java:413)
    at org.eclipse.swt.widgets.Shell.createHandle(Shell.java:448)
    at org.eclipse.swt.widgets.Control.createWidget(Control.java:497)
    at org.eclipse.swt.widgets.Scrollable.createWidget(Scrollable.java:131)
    at org.eclipse.swt.widgets.Decorations.createWidget(Decorations.java:421)
    at org.eclipse.swt.widgets.Shell.<init>(Shell.java:255)
    at org.eclipse.swt.widgets.Shell.<init>(Shell.java:332)
    at org.eclipse.jface.text.DefaultInformationControl.<init>(DefaultInformationControl.java:130)
    at org.eclipse.jface.text.DefaultInformationControl.<init>(DefaultInformationControl.java:110)
    at org.eclipse.jface.text.DefaultInformationControl.<init>(DefaultInformationControl.java:211)
    at com.ibm.sse.editor.StructuredTextViewerConfiguration$1.createInformationControl(StructuredTextViewerConfiguration.java:217)
    at org.eclipse.jface.text.AbstractInformationControlManager.getInformationControl(AbstractInformationControlManager.java:619)
    at org.eclipse.jface.text.AbstractInformationControlManager.internalShowInformationControl(AbstractInformationControlManager.java:850)
    at org.eclipse.jface.text.AbstractInformationControlManager.presentInformation(AbstractInformationControlManager.java:836)
    at org.eclipse.jface.text.AbstractInformationControlManager.setInformation(AbstractInformationControlManager.java:291)
    at org.eclipse.jface.text.contentassist.AdditionalInfoController.computeInformation(AdditionalInfoController.java:236)
    at org.eclipse.jface.text.AbstractInformationControlManager.doShowInformation(AbstractInformationControlManager.java:820)
    at org.eclipse.jface.text.AbstractInformationControlManager.showInformation(AbstractInformationControlManager.java:810)
    at org.eclipse.jface.text.contentassist.AdditionalInfoController$1.run(AdditionalInfoController.java:173)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3057)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2716)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
    at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
    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.invokeFramework(Main.java:334)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
    at org.eclipse.core.launcher.Main.run(Main.java:973)
    at org.eclipse.core.launcher.Main.main(Main.java:948)

Any ideas?

[Scott Anderson]

Any ideas?

Yep. Eclipse uses native widgets in SWT and each takes an operating resource “handle” to hang onto it. These handles are a fixed
resource that are taken up by all Windows applications, each time you boot. When you run out, you’re just out. The only way to
correct the issue I know of is to shut everything down and reboot. That frees everything up. I’ve seen this before myself, but usually
only when I’ve been running my machine for days at a time with no reboot.

[Tom Cole]

Thanks, I tried it but, no luck. Still getting the same problem. I’m running this on a Tablet PC, which used to run 3.8.4 for literally weeks without being rebooted (I tend to hibernate) with no problems. There’s a definite difference somewhere.

Is there a way I can determine if it’s eclipse or the JSP editor that’s causing the problem? At this point I’ll have to uninstall both and go back to 3.8.4, as much as I don’t want to.

It’s not like I’m lacking resources. I can run that Sun Java Studio Creator program with no problems….And I typically run Eclipse/MyEclipse, Tomcat and SQL Server desktop edition all at once. But I can’t run this 3.1/4.0M2 combination.

Thanks again.

[Scott Anderson]

How quickly are you seeing this issue? We’ve had no accounts of it internally and we typically run for weeks at a time while testing.

[Author]

Posts