Keyboard Shortcuts
Likes
- Twsapi
- Messages
Search
|
TWS will periodically "hang" on Initializing managers after daily restart and have purple grid
This will happen rarely, but couple of times in last 2 weeks, the TWS was stuck on initializing managers very likely sometime after the Daily Restart. The grids will all be purple, and the only way out is to exit and restart. When I have checked the TWS log, I dont see anything obvious( no out of memory exception etc).I have the heap size at 2 GB. I can have a lot of orders at any time. so not sure if that can cause this. This is on Windows 10 offline build 978, Nov 13 2020
This affects my trading bot which is scheduled to run every day when market opens ( esp. on days when I am out of the house). Can anyone suggest anything to look for? Thanks |
|
Re: how do I tell on the TWS app that I'm getting real time data
¿ªÔÆÌåÓýThank you Mikhail, really helpful information and thanks for the
link. I didn't know about the github.io page.? Thanks again On 8/25/21 2:18 AM, Mikhail Ershov
wrote:
If the data is delayed, you will receive a delayed tick types. |
|
Re: "The TWS build you are currently running is no longer supported."
¿ªÔÆÌåÓýIt seems I spoke too soon when I said it looks like IB really are retiring TWS972: I ran it up last night, and it worked fine, so it's clearly not dead yet. ? So apologies if I alarmed anyone unnecessarily. However, I do think it's always a bad idea to use old versions of TWS, because they are no longer updated by IB if bugs are found. ? I appreciate that some are still using 972 with IBC because it enables them to keep TWS up and running as long as they want. But that is a fight you cannot win: eventually IB will stop 972 working, and what will you do then? So even if you continue to use 972 temporarily, you really must take steps to move on to a current version sooner rather than later. ? Also mixed up in this thread is the issue of SSL: it now appears that IB are insisting on use of SSL. Fair enough, though it would have been nice to be less heavy-handed about it. ?
?
? If for some reason you can't ensure a valid jts.ini, then you'll just have to wait until I update IBC to provide a workaround (hopefully in time for the start of next week). My current thinking is to enhance IBC's existing jts.ini checking to ensure that UseSSL=true is always set. This will mean you won't be able to turn SSL off, but it appears that IB won't allow this anyway so this shouldn't be an issue. Any comments on this proposal would be welcomed, either here, or the IBC User Group, or this issue on the IBC GitHub repository: . ? Richard ? |
|
Re: how do I tell on the TWS app that I'm getting real time data
If the data is delayed, you will receive a delayed tick types.
If the data is realtime, then you won't receive delayed tick types and will receive only a real time tick types. I've seen sometimes, that even with delayed data it possible to receive real time tick types (although it's rare). I haven't noticed, probably it's impossible to receive delayed tick types if you have a real time subscription. You can search over this page with "delayed" to find the numbers of delayed ticks. |
|
Re: "The TWS build you are currently running is no longer supported."
I've gotten at least two weeks of notice every time my version of TWS was being obsoleted in the past.? This is the first time the plug has been pulled on me without warning and mid session.? As for 981 being the stable version, the first time I used it on a real account it displayed a "Price Management Algo" dialog box, which wouldn't accept input and couldn't be dismissed.? After several minutes, it crashed and I had to restart.? And now it's reported 985 is encountering the no longer supported message.? So far this has only happened outside of market hours.? It's frightening to think this might happen when the market is open. Your advice to run the latest version against a paper-trading account is good.? I'll have to start doing that. Frank
On Tuesday, August 24, 2021, 05:47:02 AM EDT, Richard L King <rlking@...> wrote:
Judging by the OP's screenshot, this is not just API incompatibility. I think IB are saying they will no longer allow you to use 972. ? I don't really understand why anyone is surprised by this, because it has happened many times before.. It would of course be better if IB gave us a week or two's warning before pulling the plug, but they've never done so before either, and why change the bad habits of a lifetime?... ? I realise that this is going to cause problems for some people, , but given that this is known behaviour from IB it's perfectly possible to avoid grief by ensuring you test your API clients (at least occasionally) against the current 'latest' (not beta) version. I run the 'latest' version all day every day on my paper-trading account (as well as the 'stable' version on my live account), and run my programs against both. That way, I can be sure that when the 'stable' version is moved up I can switch the live instance to it without problems. ? Richard ? ? From: [email protected] <[email protected]> On Behalf Of ´³¨¹°ù²µ±ð²Ô Reinold via groups.io
Sent: 24 August 2021 09:00 To: [email protected] Subject: Re: [TWS API] "The TWS build you are currently running is no longer supported." ? Did your application log files show any error messages? In case you have logged error code 503 "The TWS is out of date and must be upgraded", it may actually be an incompatibility between your API version and TWS/IBG instead of TWS/IBG and Interactive Brokers. The section says:
And the additional notes for error code 503 say:
We had that a few years back when we tried to use TickByTick data with a TWS that did not support them. The logged "msg" field of the error message was quite specific and pointed us in the right direction. I don't recall, whether TWS also had a popup error, but I believe it did. ´³¨¹°ù²µ±ð²Ô |
|
Re: "The TWS build you are currently running is no longer supported."
On Tue, Aug 24, 2021 at 04:00 PM, ´³¨¹°ù²µ±ð²Ô Reinold wrote:
Did your application log files show any error messages?´³¨¹°ù²µ±ð²Ô, no I did not receive any particular error codes such as the code 503 you mention. My client software is not using streaming data. Most of the time it is idle and not connected to Gateway. Only at specific points in time it comes to live, performs some actions which may take about 1 or 2 minutes, and then becomes idle again, disconnecting itself from Gateway. So when it tried to reconnect to Gateway at 05:00 Singapore time it resulted in an error message 2110: "Connectivity between Trader Workstation and server is broken. It will be restored automatically." The connectivity did not get restored until I restarted Gateway a couple of hours later. |
|
Re: "The TWS build you are currently running is no longer supported."
On Tue, Aug 24, 2021 at 05:46 PM, Richard L King wrote:
I think IB are saying they will no longer allow you to use 972.Richard, I know that 972 is getting of age. But it is the latest version after which IB changed the auto-logoff procedure. I wanted to benefit from IBCalpha as long as possible to keep my system running for an entire week before manually restarting it during the weekend. That's why I always resisted updating Gateway to a higher version number. But maybe my days are numbered and I will be forced to switch. |
|
Re: "The TWS build you are currently running is no longer supported."
On Tue, Aug 24, 2021 at 04:58 PM, mark collins wrote:
A similarly worded pop up turned up over a period of days on my machines, it seems to work still but it did want to engage ssl.Mark, the same happened to me. When I restarted Gateway a message appeared saying that SSL to be used (I forgot the exact wording). I okayed that and then let it continue with the logon. |
|
Re: "The TWS build you are currently running is no longer supported."
IBC did not start my gateway automatically today, and it seems to be because of a popup asking to use SSL Authentication
2021-08-24 00:50:08:503 IBC: Detected frame entitled: Authenticating...; event=Lost focus
2021-08-24 00:50:08:503 IBC: Detected frame entitled: Authenticating...; event=Deactivated
2021-08-24 00:50:08:503 IBC: Detected dialog entitled: Use SSL encryption; event=Activated
2021-08-24 00:50:08:504 IBC: Detected dialog entitled: Use SSL encryption; event=Focused --hung here without starting. I manually ran the gateway using X and clicked the Accept button and it logged in. I then exited and IBC was able to start it as that popup didn't appear again. I had the same issue with TWS 985, it also popped up the use SSL authentication when I logged in today. I had never seen that popup before. |
|
Re: "The TWS build you are currently running is no longer supported."
¿ªÔÆÌåÓýHi Richard,Hope you are well. This is probably another outdated tws version support issue but your opinion would be appreciated. I am expecting others to be similarly affected. I have been running 974.4 on a remote server without issues. I lost the connection at 4am this morning and all connections thereafter failed (no messages that this version is not supported were received). When I tested on my local machine I discovered a new prompt requesting connection with an ssl layer which needs to be manually checked. I run the remote instance with ExistingSessionDetectedAction=primary in the config file. However this setting (perhaps the whole ?configuration file) now seems to be ignored once I select the SSL layer and I now need to close all other sessions, which block, before I can launch using ibc on the remote instance.? On 24 Aug 2021, at 12:47, Richard L King <rlking@...> wrote:
|