Re: RDi 9 won't start after installing Sonicwall Global VPN client

I installed the Sonicwall Global VPN Client this morning so I could connect
to a remote system where we're doing a DR test.

When I installed the client, things that were active lost network
connection, including 5250 sessions and the UPS monitoring service. The
UPS monitoring service came back on it's own. I reestablished the 5250
sessions by doing a Connect. I decided I would just shut down RDi and
restart. It wouldn't shut down properly. I clicked the X in the upper
right of the shutdown box and the shutdown box went away. Then I clicked
the X in the upper right of RDi and finally it went away. But it wouldn't
restart. It said to see the log file.

So I decided to reboot and try it. Same error. Here is what was added to
the log file the last time I tried to restart:

!SESSION 2014-03-18 08:14:37.633
-----------------------------------------------
eclipse.buildId=unknown
java.fullversion=JRE 1.7.0 IBM J9 2.6 Windows 7 amd64-64 Compressed
References 20130617_152572 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR5_20130617_1436_B152572
JIT - r11.b04_20130528_38954ifx1
GC - R26_Java726_SR5_20130617_1436_B152572_CMPRSS
J9CL - 20130617_152572
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product com.ibm.rational.developer.ibmi.product.ide
-showlocation
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product
com.ibm.rational.developer.ibmi.product.ide -showlocation

!ENTRY com.ibm.etools.stacktool 0 0 2014-03-18 08:14:45.794
!MESSAGE plugin is early starting...

!ENTRY com.ibm.etools.stacktool 0 0 2014-03-18 08:14:45.897
!MESSAGE Save the stack tool properties file.

!ENTRY org.eclipse.osgi 4 0 2014-03-18 08:14:52.125
!MESSAGE Application error
!STACK 1
org.eclipse.swt.SWTException: Failed to execute runnable
(java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:4361)
at org.eclipse.swt.SWT.error(SWT.java:4276)
at

org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
at org.eclipse.swt.widgets.Display.release(Display.java:3814)
at org.eclipse.swt.graphics.Device.dispose(Device.java:295)
at

org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:140)
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:353)
at

org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:76)
at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:607)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
Caused by: java.lang.NullPointerException
at

org.eclipse.ui.internal.Workbench.createWorkbenchWindow(Workbench.java:1232)
at

org.eclipse.ui.internal.Workbench.getActiveWorkbenchWindow(Workbench.java:1225)
at com.ibm.cic.licensing.common.ui.Activator$1.run(Activator.java:115)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at

org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 18 more

!ENTRY com.ibm.etools.stacktool 0 0 2014-03-18 08:14:52.232
!MESSAGE plugin is stopped and cleaned up the stack tool properties file.

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.671
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.674
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.675
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.676
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.677
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.678
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.679
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.679
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.680
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.681
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.681
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.681
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.682
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.682
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.683
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.683
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.AbstractWorkingSetManager$9

!ENTRY org.eclipse.core.jobs 2 2 2014-03-18 08:14:52.684
!MESSAGE Job found still running after platform shutdown. Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.ui.internal.Workbench$54


I haven't the foggiest notion what I'm looking for. Other than the bunch
of "Job found still running after platform shutdown" but since I rebooted I
don't know what further I can do to shut anything down. Can anyone help
me?

Thanks.

--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.