IB TWS 880.2 & 880.4 hangs on startup

Discussion in 'Retail Brokers' started by rayl, Dec 14, 2007.

  1. rayl

    rayl

    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... :(
     
  2. No problems over here with 880.4

    I did have a minor problem with it not retaining my settings. Had to turn off save server settings and relaunch. Turn on server settings and save again...
     
  3. rayl

    rayl

    Sigh -- the official suggestion from CS is to delete my settings and start over. This is 100% reproducible for my settings file and I am disheartened that someone at IB can't just reproduce it and fix it.

    Strange thing -- I pulled a 2 month old settings file from backup and it behaves the same. Maybe it's some combo order I have set up or some such.

    I'll stay with 879.9 for a bit. If we get to 882 and it's still busted, I'll spend the 30 mins or so to manually recreate my setup.
     
  4. Doesnt sound like it is a TWS settings problem for you. Can you reset all your Java Prefs??? Perhaps there is a conflict. Do a backup of your IBJTS folder and start fresh. See if that resolves it. if so, then you should be able to grab your most resent Settings file (thurs.xml ??) and hopefully all will still be well.

    Hopefully that will help.
     
  5. rayl

    rayl

    Thanks -- unfortunately it IS a settings confict with 880.2/880.4 issue. If I start from a zero state (i.e., move my settings out of the way, get the help window, etc.), it works fine.... then if I go to File > Restore Settings, it will hang on restore.

    I've tried a lot of different settings file. I suspect it is a settings inherited from an old version of TWS that no longer works with 880.2+. Sigh.
     
  6. Must be a windows Java thing then.

    Unfortunately I run on a Mac, So I am at best guessworking it for you.
     
  7. No problems with either version. Windows XP SP3 v3244
     
  8. rayl

    rayl

    OK, I guess I am in the minority so will own up to recreating my settings manually either this Sunday or next Sunday. Sigh.
     
  9. maxpi

    maxpi

    I use the oldest ver. of TWS that I can get away with and then only via the API... rarely a problem of any kind.
     
  10. rayl

    rayl

    Just as an update -- after about 45 mins of manual merging of tws.xml files, I think I've isolated the problem to some settings I had for ClickTrader|0 and ClickTrader|1 (which I assume are button trader).

    Of course, as luck would have it, the server shutdown started -- but I will post an update on Sunday if this is indeed the problem or not.

    i.e., I think if I take my old 879.9 tws.xml file and delete these 2 sections, it will work. I thought I saw it working but need to do a clean test to confirm -- when IB comes back up.
     
    #10     Dec 14, 2007