Does anyone else have trouble getting TWS 880.2 or later (went into prod as of Tue morning) to load? I've isolated it to my settings. If I both delete my settings and uncheck store settings on server, it loads fine (but am stuck with a default configuration).
And if I then take the default starting point and pick Restore Settings, it hangs on the restore.
I've started to "recreate" my world but decided to revert to 879.9 which works fine.
The log ends at the hang with:
LS 09:26:47:806 AWT-EventQueue-0: Error reading settings file C:\Jts\dj [name edited] \tws.xml
LS java.lang.NullPointerException
at jsetting.DeepBookContent.g(DeepBookContent.java:86)
at jsetting.WindowsSettings.a(WindowsSettings.java:119)
at jsetting.WindowsSettings.a(WindowsSettings.java:91)
at trader.workspace.WorkspaceCollection.a(WorkspaceCollection.java:61)
at jsetting.Settings.e(Settings.java:557)
at jsetting.Settings.d(Settings.java:872)
at jsetting.Settings.c(Settings.java:816)
at jclient.mf.If(mf.java:6022)
at jclient.mf.<init>(mf.java:1007)
at jclient.LoginWindow.b(LoginWindow.java:1142)
at jconnection.o.run(o.java:1134)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
LS 09:26:48:902 JTS-CCPPing-9: Warning: not received heartbeat at 11000
LS 09:26:49:902 JTS-CCPPing-9: Warning: not received heartbeat at 12000
LS 09:26:50:902 JTS-CCPPing-9: Warning: not received heartbeat at 13000
LS 09:26:51:902 JTS-CCPPing-9: Warning: not received heartbeat at 14000
LS 09:26:52:902 JTS-CCPPing-9: Warning: sending test request at 15000
LS 09:26:53:136 JTS-LogonDispatcher-8: Received heartbeat
LS 09:27:03:902 JTS-CCPPing-9: Warning: not received heartbeat at 26000
LS 09:27:04:902 JTS-CCPPing-9: Warning: not received heartbeat at 27000
LS 09:27:05:902 JTS-CCPPing-9: Warning: not received heartbeat at 28000
LS 09:27:06:902 JTS-CCPPing-9: Warning: not received heartbeat at 29000
LS 09:27:07:902 JTS-CCPPing-9: Warning: sending test request at 30000
LS 09:27:08:137 JTS-LogonDispatcher-8: Received heartbeat
LS 09:27:18:902 JTS-CCPPing-9: Warning: not received heartbeat at 41000
LS 09:27:19:902 JTS-CCPPing-9: Warning: not received heartbeat at 42000
LS 09:27:20:902 JTS-CCPPing-9: Warning: not received heartbeat at 43000
LS 09:27:21:902 JTS-CCPPing-9: Warning: not received heartbeat at 44000
LS 09:27:22:902 JTS-CCPPing-9: Warning: sending test request at 45000
LS 09:27:23:137 JTS-LogonDispatcher-8: Received heartbeat
I have a ticket open (w/copies of my settings, the log from 880.2 and just added the log from 880.4)... and also emailed settings & 880.2 log to DAV previously.
Had the "customary" response on the ticket -- try an older tws.xml file.... but I've tried several of them. I suspect I must have some setting for some time that is causing the bug to show.
Sigh -- I guess if we go to 881 and the problem still exists, I will have to manually recreate my settings...
And if I then take the default starting point and pick Restore Settings, it hangs on the restore.
I've started to "recreate" my world but decided to revert to 879.9 which works fine.
The log ends at the hang with:
LS 09:26:47:806 AWT-EventQueue-0: Error reading settings file C:\Jts\dj [name edited] \tws.xml
LS java.lang.NullPointerException
at jsetting.DeepBookContent.g(DeepBookContent.java:86)
at jsetting.WindowsSettings.a(WindowsSettings.java:119)
at jsetting.WindowsSettings.a(WindowsSettings.java:91)
at trader.workspace.WorkspaceCollection.a(WorkspaceCollection.java:61)
at jsetting.Settings.e(Settings.java:557)
at jsetting.Settings.d(Settings.java:872)
at jsetting.Settings.c(Settings.java:816)
at jclient.mf.If(mf.java:6022)
at jclient.mf.<init>(mf.java:1007)
at jclient.LoginWindow.b(LoginWindow.java:1142)
at jconnection.o.run(o.java:1134)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
LS 09:26:48:902 JTS-CCPPing-9: Warning: not received heartbeat at 11000
LS 09:26:49:902 JTS-CCPPing-9: Warning: not received heartbeat at 12000
LS 09:26:50:902 JTS-CCPPing-9: Warning: not received heartbeat at 13000
LS 09:26:51:902 JTS-CCPPing-9: Warning: not received heartbeat at 14000
LS 09:26:52:902 JTS-CCPPing-9: Warning: sending test request at 15000
LS 09:26:53:136 JTS-LogonDispatcher-8: Received heartbeat
LS 09:27:03:902 JTS-CCPPing-9: Warning: not received heartbeat at 26000
LS 09:27:04:902 JTS-CCPPing-9: Warning: not received heartbeat at 27000
LS 09:27:05:902 JTS-CCPPing-9: Warning: not received heartbeat at 28000
LS 09:27:06:902 JTS-CCPPing-9: Warning: not received heartbeat at 29000
LS 09:27:07:902 JTS-CCPPing-9: Warning: sending test request at 30000
LS 09:27:08:137 JTS-LogonDispatcher-8: Received heartbeat
LS 09:27:18:902 JTS-CCPPing-9: Warning: not received heartbeat at 41000
LS 09:27:19:902 JTS-CCPPing-9: Warning: not received heartbeat at 42000
LS 09:27:20:902 JTS-CCPPing-9: Warning: not received heartbeat at 43000
LS 09:27:21:902 JTS-CCPPing-9: Warning: not received heartbeat at 44000
LS 09:27:22:902 JTS-CCPPing-9: Warning: sending test request at 45000
LS 09:27:23:137 JTS-LogonDispatcher-8: Received heartbeat
I have a ticket open (w/copies of my settings, the log from 880.2 and just added the log from 880.4)... and also emailed settings & 880.2 log to DAV previously.
Had the "customary" response on the ticket -- try an older tws.xml file.... but I've tried several of them. I suspect I must have some setting for some time that is causing the bug to show.
Sigh -- I guess if we go to 881 and the problem still exists, I will have to manually recreate my settings...