Placed order at open, now disconnected from IBKR
- This topic has 16 replies, 3 voices, and was last updated 2 years ago by
.
-
Anyone have this occur before? I placed an order at the open, and PRT disconnected from IBKR and will not reconnect. Luckily I’m in paper, but…..
RubberToe,
If this is the same as I ever back had it, it is related to a certain shutdown and start sequence to recover from it. I have written it somewhere for myself (or for PRT to solve). This is from a time I tested this kind of connection (which relates to the API version). In the end this never bothered me again because I knew what not to do in order to avoid the issue all together. Btw, this was Live, not Paper.
Later today I will try to find this description and lay it out. It will be the most vague (because the issue itself is vague) …
Small question : As far as I know, the API version is not promoted. Would you happen to know why you are using this version ? Is this possibly because you used TWS already and thus have a direct account by IBKR already ? … IOW, do notice that as far as I can tell, the API can be avoided. This is then what I would call the PRT-IB version. You would still be using PRT, but you will NOT need to have TWS open in order to trade and maintain your positions. As a matter of fact you will not need to have open anything, because PRT runs on a server, you interacting with that by means of the PRT platform. This is super convenient …
You would still be able to use TWS in parallel. Both platforms (TWS and PRT) interact in real time with each other.Peter
1 user thanked author for this post.
It seems that I never made the formal report about it. This is my own text from 6 or so months back, written to PRT :
What I certainly do notice is that PRT has difficulties in initialising the connection with TWS. I mean, by now I have collected quite some combinations of situations which work and which will not work (unless some specific “reset” sequence is applied). I will sent a report about this in a later stage – when I myself see better through what’s happening.
On a side note : I have worked with the API myself a little (programmed with it), so I kind of know a bit how TWS can respond to third party connections.And now it connects, after a whole day of fighting with it, grrrrrrrr. I restarted IBKR for the 5th time and it loaded an update, and a ton of alarms came in to PRT, like they were stored in a que all day.
Yes, I have pictures of those stacked messages too.
From the same sequence of screenshots I made about this, I also find the one you see in the first attachment (also more than one message at the same time). Notice that this is PRT showing the message, while the content of the message seems wrong, but it not really (as it seems). I mean, look at the background in the 2nd attachment. That is TWS which is inactive. As far as I can recall this initiates such a fault situation because you yourself (in my case, that is) caused TWS to disconnect, for example by means of making a connection with the (IBKR) mobile app. THAT now chokes the PRT connection with TWS (quite obviously) but that is the unexpected situation. Do notice that TWS stays live for a minute or so WHILE it is officially not connected to IB indeed (thus, content of the message would be correct).
It will now require that special reset sequence, I really forgot. I definitely recall that either PRT or TWS needed to be restarted TWICE. Something like
- Start TWS
- Start PRT
- Close TWS
- Start TWS
or
- Start PRT
- Stat TWS
- Close PRT
- Start PRT
All relates to the (important !) message you see in the 3rd attachment. Thus, you MUST allow TWS to detect the incoming PRT connection. Hence, if PRT already runs prior to starting TWS, this will not happen. This is how the startup sequence becomes crucial.
As a kind of bonus, I added the 4th attachment. I am pretty surely recalling that despite this message, this was NOT the case. All looked OK (connection button is green) but nothing worked for real. So you’d need to keep in touch with that too …
Please remember, you can work directly with PRT and IB. This is probably a matter of asking your PRT support to set it up for you ?
1 user thanked author for this post.
If you are still there … it only now occurs to me (I asked) that while I have been beta testing the API, now indeed people over at your areas, actually use it for the first time. Read : this has been insufficiently (beta) tested, and already my own tests were unfinished (they are from half of December 2020).
So … people in your area (say North America) never could use PRT for real trading. I did not know this …On a side note, normally PRT support can “look” in your environment when you send a so-called Technical Report. But with the API this can not work, as you work locally (and not on a server, as I laid out).
I just set PRT support to this issue again, explained it, and especially explained how the issue can be triggered (which is always crucial for bug solving). How it can be reset should be easy, and at least on that they will work (should be soon).
It can be so that you’ll hear it directly from PRT support, because they told me that someone already told about the very same issue. If this was you who told them, you will hear it directly from them.
1 user thanked author for this post.
Find exclusive trading pro-tools on 
