Community
Participate
Working Groups
I have seen this when trying to connect to a couple different systems. The system view and active jobs don't have any trouble, but the inactive jobs view only shows an error message. java.lang.NullPointerException at org.eclipse.ptp.rm.lml.ui.views.TableView.createColumns(TableView.java:495) at org.eclipse.ptp.rm.lml.ui.views.TableView.createTable(TableView.java:645) at org.eclipse.ptp.rm.lml.ui.views.TableView.access$5(TableView.java:643) at org.eclipse.ptp.rm.lml.ui.views.TableView$LMLTableListListener$1.run(TableView.java:89) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.ptp.rm.lml.ui.UIUtils$7.run(UIUtils.java:194) at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:164) at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:158) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) 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:344) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Wyatt, can you describe more in detail how to reproduce the problem. Do you switch from one RM to another one, or from the Active Jobs view to the Inactive Jobs view? Is this problem maybe related to a specific system, or does the problem occurs in general? What for batch systems do you want to connect to? Which PTP version is running on the systems?
Created attachment 204654 [details] Workaround for the problem I had a closer look today and implemented a workaround.
Can you set your line width to 132, reformat, then regenerate this patch? This will reduce the number of changes significantly. To set your line width, Preferences>Java>Formatter, then Edit... the active profile. Change maximum line length on the Line Wrapping and Comments tabs.
Created attachment 205004 [details] Workaround for the problem
Workaround works.
