search

IbcAlpha / IBC

Automation of Interactive Brokers TWS. You can download the latest release here: https://github.com/ibcalpha/ibc/releases/latest
GNU General Public License v3.0
1.03k stars 181 forks source link

IBC 3.15.2 failed to restart TWS 10.25.1n (paper) #238

Closed akatsev closed 8 months ago

akatsev commented 10 months ago

Hi, I have ran this configuration for a few days without problems, but today I saw that not IBC nor TWS are not running. I tried to restart IBC twice, but without success. After showing dialog "This is not a brokerage account..." both IBC and TWS get closed without any notification/message. I tried this on my another computer (the same configuration, other account) and this worked perfectly. IBC-3.15.2_TWS-1025_FRIDAY.txt

Log file is attached (all times in UTC) Thank you, A. Katsev.

rlktradewright commented 10 months ago

What's happening here is that something is killing the Java process that runs IBC and TWS. It's not anything in IBC itself.

The relevant message in the logfile is:

Error level is 9

which is written by the batch script after IBC exits. Whenever IBC deliberately exits with a non-zero error level, it also logs an explanatory message, and a message containing the error level before exiting, and the script then also logs the above message, so the logfile ends up with three distinct consecutive entries. Since this isn't the case here, it confirms that it wasn't IBC that exited, but there was an abrupt forced termination of the program (and error level 9 from a Java program means precisely that).

So I've no idea what might have caused that: it is definitely something external to IBC, For example using Task Manager to terminate the running java.exe program would have this effect.

akatsev commented 10 months ago

OK, thank you, it's quite helpful. I'll continue my investigations. Thank you very much, A. Katsev.

пт, 24 нояб. 2023 г. в 12:21, Richard L King @.***>:

What's happening here is that something is killing the Java process that runs IBC and TWS. It's not anything in IBC itself.

The relevant message in the logfile is:

Error level is 9

which is written by the batch script after IBC exits. Whenever IBC deliberately exits with a non-zero error level, it also logs an explanatory message, and a message containing the error level before exiting, and the script then also logs the above message, so the logfile ends up with three distinct consecutive entries. Since this isn't the case here, it confirms that it wasn't IBC that exited, but there was an abrupt forced termination of the program (and error level 9 from a Java program means precisely that).

So I've no idea what might have caused that: it is definitely something external to IBC, For example using Task Manager to terminate the running java.exe program would have this effect.

— Reply to this email directly, view it on GitHub https://github.com/IbcAlpha/IBC/issues/238#issuecomment-1825600088, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE44OADUQEXYUBITIZJ2NGTYGCGOFAVCNFSM6AAAAAA7Y6HBZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRVGYYDAMBYHA . You are receiving this because you authored the thread.Message ID: @.***>