This is what I am getting today. I never noticed so many lost connections before today. The datafeed has never stopped working during the lost connections. But my concern is that I can't place or cancel orders when the connectivity between IB and TWS is lost. Am I the only one with this problem today with IB? I am using ActiveX connection to TWS, and requesting only ESU6 live data. I doubt this would be the cause of the lost connectivity between IB and TWS. I did not have this problem before today. And today happened to be a heavy trading day for ESU6 so far, 11:40 am. ------------------------------------------------------------------------------------ Market data farm connection is OK:usfuture 19-Jul-2006 08:55:21 Market data farm connection is OK:usfarm 19-Jul-2006 08:55:21 HMDS data farm connection is OK:ushmds2a 19-Jul-2006 08:55:21 HMDS data farm connection is inactive but should be available upon demand.:ushmds2a 19-Jul-2006 08:57:18 Connectivity between IB and TWS has been lost. 19-Jul-2006 08:58:07 Connectivity between IB and TWS has been lost. 19-Jul-2006 09:01:15 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 09:03:08 Historical Market Data Service query message:HMDS server connection was successful. 19-Jul-2006 09:04:30 HMDS data farm connection is OK:ushmds2a 19-Jul-2006 09:04:30 Connectivity between IB and TWS has been lost. 19-Jul-2006 09:08:10 HMDS data farm connection is inactive but should be available upon demand.:ushmds2a 19-Jul-2006 09:09:30 Connectivity between IB and TWS has been lost. 19-Jul-2006 09:11:19 No historical data query found for ticker id:88 19-Jul-2006 09:12:27 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 09:13:11 Historical Market Data Service query message:HMDS server connection was successful. 19-Jul-2006 09:14:10 HMDS data farm connection is OK:ushmds2a 19-Jul-2006 09:14:10 HMDS data farm connection is inactive but should be available upon demand.:ushmds2a 19-Jul-2006 09:17:10 Connectivity between IB and TWS has been lost. 19-Jul-2006 09:18:11 Connectivity between IB and TWS has been lost. 19-Jul-2006 09:21:17 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 09:23:12 Connectivity between IB and TWS has been lost. 19-Jul-2006 09:28:13 Connectivity between IB and TWS has been lost. 19-Jul-2006 09:31:21 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 09:33:16 Connectivity between IB and TWS has been lost. 19-Jul-2006 09:38:15 Connectivity between IB and TWS has been lost. 19-Jul-2006 09:41:23 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 09:43:15 Connectivity between IB and TWS has been lost. 19-Jul-2006 09:48:18 Connectivity between IB and TWS has been lost. 19-Jul-2006 09:51:26 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 09:53:20 Connectivity between IB and TWS has been lost. 19-Jul-2006 09:58:20 Connectivity between IB and TWS has been lost. 19-Jul-2006 10:01:31 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 10:03:21 Connectivity between IB and TWS has been lost. 19-Jul-2006 10:08:23 Connectivity between IB and TWS has been lost. 19-Jul-2006 10:11:34 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 10:13:25 Connectivity between IB and TWS has been lost. 19-Jul-2006 10:18:26 Connectivity between IB and TWS has been lost. 19-Jul-2006 10:21:33 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 10:23:29 Connectivity between IB and TWS has been lost. 19-Jul-2006 10:28:29 Connectivity between IB and TWS has been lost. 19-Jul-2006 10:31:35 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 10:33:30 Connectivity between IB and TWS has been lost. 19-Jul-2006 10:38:31 Connectivity between IB and TWS has been lost. 19-Jul-2006 10:41:38 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 10:43:30 Connectivity between IB and TWS has been lost. 19-Jul-2006 10:48:31 Connectivity between IB and TWS has been lost. 19-Jul-2006 10:51:37 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 10:53:32 Connectivity between IB and TWS has been lost. 19-Jul-2006 10:58:34 Connectivity between IB and TWS has been lost. 19-Jul-2006 11:01:39 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 11:03:34 Connectivity between IB and TWS has been lost. 19-Jul-2006 11:08:37 Connectivity between IB and TWS has been lost. 19-Jul-2006 11:11:45 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 11:13:38 Connectivity between IB and TWS has been lost. 19-Jul-2006 11:18:38 Connectivity between IB and TWS has been lost. 19-Jul-2006 11:21:47 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 11:23:39 Connectivity between IB and TWS has been lost. 19-Jul-2006 11:28:39 Connectivity between IB and TWS has been lost. 19-Jul-2006 11:31:46 Connectivity between IB and TWS has been restored - data maintained. 19-Jul-2006 11:33:40
Just as a FWIW - IB may indeed have a problem - but 90% of the time when I have had connectivity issues with TWS, it was NOT IB. It was my crappy ISP. If we don't get a few more (lots more) people with the same problem, I think it would be safe to say it is local to your network. Mine is working fine today. Good luck.
does it still do it with active x,not active? just the tws?mine was screwed up yesterday and it was my isp. they fixed it
Battle, How did your ISP screw up the connection? I am still having the same problem more or less up to now. The datafeed has been alive all day long, it's just the IB to TWS connection.