My rich client crashes on invoking through eclipse, after I installed the Eclim plugin on eclipse.

[narula]

Hello all,

My rich client application which was coming up before through Ecipse, crashes now after I have installed the Eclim plugin to the Eclipse software. Could you please tell me what is going on?

Any help will be greatly appreciated at this point. Thanks.

I am pasting the syslog below:

WARN : 13:27:58,740  - TcLogger$IC_PrintStream.log:?

java.lang.IllegalArgumentException: The handle object must not have a zero-length identifier

at org.eclipse.core.commands.common.HandleObjectManager.checkId(HandleObjectManager.java:60)

at org.eclipse.core.commands.contexts.ContextManager.getContext(ContextManager.java:192)

at org.eclipse.ui.internal.contexts.ContextService.getContext(ContextService.java:191)

at com.teamcenter.rac.aifrcp.KeyBindingCommandContexts.defineRuntimeContexts(Unknown Source)

at com.teamcenter.rac.aifrcp.KeyBindingCommandContexts.initialize(Unknown Source)

at com.teamcenter.rac.aifrcp.ApplicationWorkbenchAdvisor.preStartup(Unknown Source)

at org.eclipse.ui.internal.Workbench$31.runWithException(Workbench.java:1564)

at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)

at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)

at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)

at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)

at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2537)

at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427)

at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663)

at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)

at com.teamcenter.rac.aifrcp.Application.runApplication(Unknown Source)

at com.teamcenter.rac.aifrcp.Application.start(Unknown Source)

at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)

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:597)

at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)

at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)

at org.eclipse.equinox.launcher.Main.run(Main.java:1407)

at org.eclipse.equinox.launcher.Main.main(Main.java:1383)

ERROR: 13:27:58,743  - TcLogger$IC_LogListener.logging:?

org.eclipse.core.runtime - org.eclipse.ui - 0 - Unhandled event loop exception

java.lang.IllegalArgumentException: The handle object must not have a zero-length identifier

at org.eclipse.core.commands.common.HandleObjectManager.checkId(HandleObjectManager.java:60)

at org.eclipse.core.commands.contexts.ContextManager.getContext(ContextManager.java:192)

at org.eclipse.ui.internal.contexts.ContextService.getContext(ContextService.java:191)

at com.teamcenter.rac.aifrcp.KeyBindingCommandContexts.defineRuntimeContexts(Unknown Source)

at com.teamcenter.rac.aifrcp.KeyBindingCommandContexts.initialize(Unknown Source)

at com.teamcenter.rac.aifrcp.ApplicationWorkbenchAdvisor.preStartup(Unknown Source)

at org.eclipse.ui.internal.Workbench$31.runWithException(Workbench.java:1564)

at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)

at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)

at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)

at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)

at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2537)

at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427)

at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663)

at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)

at com.teamcenter.rac.aifrcp.Application.runApplication(Unknown Source)

at com.teamcenter.rac.aifrcp.Application.start(Unknown Source)

at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)

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:597)

at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)

at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)

at org.eclipse.equinox.launcher.Main.run(Main.java:1407)

at org.eclipse.equinox.launcher.Main.main(Main.java:1383)

TcMem Binding Implementation 1.0.0(1.0.0) initialized.

FCC interface version fms.9.1.0.20120302.00.

Loaded implementation library 'C:\splm\tc9-rtm-4t\tccs\lib\FCCClientProxyDllv9064.dll'.

FCC Interface Implementation fms.9.1.0.20120302.00 initialized.

[Eric Van Dewoestine]

Looking at the eclipse source for the following part of the stack
trace:

java.lang.IllegalArgumentException: The handle object must not have a zero-length identifier
at org.eclipse.core.commands.common.HandleObjectManager.checkId(HandleObjectManager.java:60)
at org.eclipse.core.commands.contexts.ContextManager.getContext(ContextManager.java:192)
at org.eclipse.ui.internal.contexts.ContextService.getContext(ContextService.java:191)
at com.teamcenter.rac.aifrcp.KeyBindingCommandContexts.defineRuntimeContexts(Unknown Source)

I don't see how eclim would have any affect here since the code of
those last 3 calls are just:

org.eclipse.ui.internal.contexts.ContextService.getContext :191
public final Context getContext(final String contextId) {
return contextManager.getContext(contextId); // line 191
}

org.eclipse.core.commands.contexts.ContextManager.getContext :192
public final Context getContext(final String contextId) {
checkId(contextId); // line 192

org.eclipse.core.commands.common.HandleObjectManager.checkId :60
protected final void checkId(final String id) {
if (id == null) {
throw new NullPointerException(
"A handle object may not have a null identifier"); //$NON-NLS-1$
}

if (id.length() < 1) {
throw new IllegalArgumentException( // line 60
"The handle object must not have a zero-length identifier"); //$NON-NLS-1$
}
}

So whatever value com.teamcenter.rac.aifrcp.KeyBindingCommandContexts
is passing in for the context id must have a length of < 1. I don't
have the code for that class so I can't see where it's getting context
ids from, but I can't think of any way that eclim could be causing
this. If you can debug that 'defineRuntimeContexts' method showing
eclim as the cause I'd be happy to investigate.

--
eric