Exiting with "Attempted to append to non-started appender e" about ibc

[rlktradewright]

The thing to note is that the "Attempted to append to non-started appender e" messages are actually output to StdOut by the Gateway itself when it shuts down: they're not anything to do with IBC (but IBC logs any output to StdOut).

So the Gateway has simply decided to shut down here. What's odd is the 'Detected frame entitled: DUXXXXXX Exit Session Setting' message. I've never seen the Gateway display this dialog before, only TWS, which displays it a few minutes before the configured autologoff time.

Perhaps this is some new behaviour in Gateway 975? I havent actually got round to testing 975 yet, so it looks like I'd better get started with it, and see if i can understand what's happening here.

In the meantime I suggest you revert to 974, unless there is something new in 975 that you need.

[tredondo]

Thanks for looking into this.

I couldn't find 974 among the downloads but I've reverted to 972.1s.

[rlktradewright]

Ok, I've checked this out, and unfortunately IBKR have introduced the autologoff mechanism into the Gateway, the same as TWS.

And, like TWS, if you start Gateway from the ibgateway.exe program or the desktop icon (or the Linux script), you can use the 'Auto restart' option to keep it running all week.

However, IBC can't work with the .exe/script: it is limited to invoking Gateway via the relevant Java entrypoint, and doing so doesn't offer the 'Auto restart' option.

So, as with TWS 974 onwards, if you want to use Gateway 975 with IBC and keep it running, you'll have to set the autologoff time to an appropriate value and arrange to restart IBC automatically every day shortly after that time.

Note that this will of course mean that your API applications have to be able to cope with disconnections from Gateway.

The only alternative is to give up using IBC with Gateway and run it from the .exe (or Linux script). This of course means you'll have to login manually once a week.

[tredondo]

I saw this error again today, while using Gateway 972.1t on Ubuntu. I understand the error is generated by Gateway, so there might be nothing IBC could do, but in case there is, I've attached the log of this new occurrence.

appender_log_2019-07-04.txt

[rlktradewright]

No there is nothing you can do about this error message. Just ignore it.

You already gave me the log, so why post it again?

And in future, please attach log files rather than quoting them.

[tredondo]

Sorry about that. Cleaner indeed to attach the log; I've edited my comment above.

The reason I posted the new log was in hope it would help identify anything IBC could do to improve the situation. The first log I posted seemed useful,

What's odd is the 'Detected frame entitled: DUXXXXXX Exit Session Setting' message. I've never seen the Gateway display this dialog before