It's all about the answers!

Ask a question

Exception in RTC classes using ShellEd


Chris Barlock (18814337) | asked Jul 14 '17, 4:50 p.m.

I'm using Eclipse Neon.3 Java EE with RTC 6.0.2 and ShellEd 5.x.  Since accepting the latest updates to all installed components, the Outline view of scripts opened in ShellEd (part of the DLTK) no longer works.  All I see is the white 'C' icon in a green circle and the name of the script -- but none of the function names or other items in the script that normally appear in the outline.  I note the following in the error log:

com.ibm.team.filesystem.client.FileSystemException: Resource '/ /start-mongodb.sh' does not exist. at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaUtil.isShareRoot(CopyFileAreaUtil.java:179) at com.ibm.team.filesystem.ide.ui.internal.util.NestedLoadPropertyTester.test(NestedLoadPropertyTester.java:35) at org.eclipse.core.internal.expressions.Property.test(Property.java:58) at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:100) at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) at org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementExpression.java:55) at org.eclipse.ui.internal.ObjectActionContributor$ObjectContribution.isApplicableTo(ObjectActionContributor.java:368) at org.eclipse.ui.internal.ObjectActionContributor.isApplicableTo(ObjectActionContributor.java:238) at org.eclipse.ui.internal.ObjectContributorManager.isApplicableTo(ObjectContributorManager.java:302) at org.eclipse.ui.internal.ObjectActionContributorManager.contributeObjectActions(ObjectActionContributorManager.java:89) at org.eclipse.ui.internal.PopupMenuExtender.addObjectActions(PopupMenuExtender.java:317) at org.eclipse.ui.internal.PopupMenuExtender.menuAboutToShow(PopupMenuExtender.java:394) at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:339) at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:470) at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:465) at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:497) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:256) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4418) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1084) at org.eclipse.swt.widgets.Control.WM_INITMENUPOPUP(Control.java:5160) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4828) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:359) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1656) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2199) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5110) at org.eclipse.swt.internal.win32.OS.TrackPopupMenu(Native Method) at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:262) at org.eclipse.swt.widgets.Display.runPopups(Display.java:4277) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3818) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:508) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) at org.eclipse.equinox.launcher.Main.run(Main.java:1519) at org.eclipse.equinox.launcher.Main.main(Main.java:1492) Caused by: org.eclipse.core.internal.resources.ResourceException: Resource '/ /start-mongodb.sh' does not exist. at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:335) at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:209) at org.eclipse.core.internal.resources.Resource.checkAccessibleAndLocal(Resource.java:215) at org.eclipse.core.internal.resources.Resource.getPersistentProperty(Resource.java:1151) at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaUtil.isShareRoot(CopyFileAreaUtil.java:175) ... 53 more

where, in this case, start-mongodb.sh is the name of the script. I opened a bug report against ShellEd, but ShellEd installed into a fresh Eclipse without RTC works just fine.  Also, I uninstalled ShellEd 5.8 and reverted to 5.6 in my Eclipse/RTC environment and it has the same Outline failure as 5.8.  Also, since this Exception is in the com.ibm.team classes, this looks more and more like an RTC bug.  Is "Open a Service Ticket" the right way to get this addressed?


Comments
Chris Barlock commented Aug 10 '17, 1:26 p.m.

  I just installed the Eclipse Oxygen Java EE bundle and added RTC and ShellEd to it.  Same problem.  What is the current mechanism for opening RTC bug reports?  Is it "Open a Service Ticket?"


Ian Wark commented Aug 10 '17, 9:22 p.m.

If you have entitlement to raise a PMR via SR or otherwise, that is a good method to investigate. You can also raise a Defect type workitem in jazz.net directly, but there is no guarantee the issue would get attention.

There is an issue with some duplicate bundles in RTC media that has affected some clients with third party Eclipse plugins. Are you installing RTC via p2? If not, I would suggest you should definitely try that, as it works around the duplicate bundle issue.
https://jazz.net/downloads/rational-team-concert/releases/6.0.2/RTC-Client-p2Repo-6.0.2.zip


Chris Barlock commented Aug 11 '17, 9:21 a.m.

Yes, I installed via p2.

Be the first one to answer this question!


Register or to post your answer.