开云体育

screenshots included now Van: rik dieltjens <rik_en_veronique1@...> Verzonden: woensdag 12 maart 2025 8:16 Aan: ibcalpha@groups.io <ibcalpha@groups.io> Onderwerp: FW: [ibc] port already in use Hi Richard, as mentioned yesterday I added some comments in my own logfile to see what happens after the restart. This morning I saw the same error message, and again twice the same instance : account -86 is open and normally reacting. The same account -86 is still (or again?) there, but the screen is grey and it does not respond to anything. You will find 2 screenshots, both with the grey screen. On the first my pointer is in the lower tab menu above the account -86, so the account number is shown. On the second, my pointer is above another account tab (7 tabs more to the left or to the right), showing the same account number. That's the best I could get to show you what I try to tell. My code in the background stops checking after 22:00 and does not start before 8:45 in the morning. The auto-restart is just before midnight. I took the screenshot this morning around 8:30. So the code did not do anything, which is confirmed by my logfile. (the code runs "/opt/ibc/twsstart4080.sh" every 5' during the day, from 8:45 untill 22:00 : as far as I know this will open the 4080 instance if not open yet, or do nothing if already open, please correct me if I'm wrong). If you can't think of any other reason, I will change the restart time and try to see what happens at that time. Thanks anyway, rik Van: rik dieltjens <rik_en_veronique1@...> Verzonden: dinsdag 11 maart 2025 16:18 Aan: ibcalpha@groups.io <ibcalpha@groups.io> Onderwerp: Re: [ibc] port already in use Thanks for your reaction, Richard. I have indeed running a code that is checking if some instance has been closed while it shouldn't. This also runs for many years now. I will add comment lines to my logfile to check if this code tries to start a new instance at some time where the ibc-log says that it is open already. Anyway, thanks for the tip. best regards rik Van: ibcalpha@groups.io <ibcalpha@groups.io> namens Richard L King <rlking@...> Verzonden: dinsdag 11 maart 2025 10:51 Aan: ibcalpha@groups.io <ibcalpha@groups.io> Onderwerp: Re: [ibc] port already in use rik As far as I can tell from the logfile, IBC is behaving fine. The restart does complete successfully, and then at 2025-03-11 08:40:09:452 the program shuts down: I presume this is because at this point you closed it manually, because it was displaying the ‘port already in use’ dialog? All the evidence points to there really being another instance configured with the same API port. When the first instance closes for restart at 2025-03-10 23:49:02, it really has shut down – there is no possibility that it’s still running. And yet you say ‘one instance (always the same) did not close as it should (it is still open, and does not react on anything)’. Can you get a screenshot showing this supposedly blocked instance, the new instance, and the error message together? What seems most likely to me is that the original instance has indeed shut down and restarted successfully (which is what the log shows), and another new instance has somehow been started and it is this one that is showing the error dialog. I have no idea why that might have happened: perhaps you are doing periodic restarts using Task Scheduler to catch cases where IBC/TWS has crashed, and this just happens to be at the same time as the auto-restart? So from my point of view I can’t see anything wrong here: there doesn’t appear to be an IBC problem. However I do note that you’re running a rather old version of IBC, and I would encourage you to move to the latest version. Richard From: ibcalpha@groups.io <ibcalpha@groups.io> On Behalf Of rik . via groups.io Sent: 11 March 2025 08:03 To: ibcalpha@groups.io Subject: [ibc] port already in use Hello, I'm using ibc for years now, starting multipal instances on sunday or monday, and let them restart overnight until the weekend. Since a few weeks I'm getting the error "port already in use" (see printscreen) on the first res

Hello, I'm using ibc for years now, starting multipal instances on sunday or monday, and let them restart overnight until the weekend. Since a few weeks I'm getting the error "port already in use" (see printscreen) on the first restart moment, so I see it on monday or tuesday morning. This is because one instance (always the same) did not close as it should (it is still open, and does not react on anything). The new instance opens well but cannot use the API port as it seems to be still in use by the blocked instance. The only thing I can do is close everything but the blocked instance, restart my pc and start all over again. This happens only after the first overnight restart. The rest of the week everything ngoes fine (until now...). I have no clue what or where to look for. The log is attached (this week I started on monday, so I saw the error this tuesday morning). Every help is welcome. Thanks, rik

Hi all, I’m currently trying to set up IB Gateway 10.30.1s with IBC 3.20.0 on my Raspberry Pi, using a custom Dockerfile based on Ubuntu 24.04 for running IB on my raspi (ARM64). ```FROM ubuntu:24.04 AS setup ENV IB_GATEWAY_VERSION=10.30.1s ENV IB_GATEWAY_RELEASE_CHANNEL=stable ENV IBC_VERSION=3.20.0 ``` For Java, I’m using an ARM-compatible version of the JDK from BellSoft: bellsoft-jre21.0.5+11-linux-aarch64. However, I’m encountering an issue when running the gateway. The log shows this error: ```java.lang.reflect.InaccessibleObjectException: Unable to make private static javax.swing.UIManager$LAFState javax.swing.UIManager.getLAFState() accessible: module java.desktop does not "opens javax.swing" to unnamed module @8f4ea7c``` it appears that the issue is related to IBC's interaction with Java's module system. Specifically, it seems to be a problem with access restrictions on Java’s ```javax.swing``` package, which is enforced by the java.desktop module in newer Java versions I’ve considered adding the following JVM argument to the ```ibgateway.vmoptions``` file: ```--add-opens java.desktop/javax.swing=ALL-UNNAMED``` This argument would open up the necessary parts of ```javax.swing``` to the unnamed module and may allow the gateway to function properly. At this point, I’m unsure whether the root cause is due to IBC not being fully compatible with Java 21 or if there is another configuration issue. Has anyone else faced this problem or have any advice on how to properly configure IBC with Java 21 in a Docker environment? Many thanks from Paris John

Greetings, Based on the recommendation from, I like to set Choose "Auto Restart" instead of "Auto Logoff" in the "Auto Logoff Timer" section. https://ibkrcampus.com/campus/ibkr-api-page/twsapi-doc/#bp-reauthenticate When I start my IBC with the default Confi.ini, I get this: What Config.ini settings changes "Auto logoff" to "Auto Restart"? I am aware of these settings, but not sure which one changes the radio button? AutoLogoffTime= AutoRestartTime= ColdRestartTime= Thank you!

A little bit of background, my instance of IBC is installed on virtual machine which automatically opens an tmux session which has an env session ran within it. The reason I am doing this is because I want IBC to run in the background void of any windows on my local computer. I tried to run the gatewaystart.sh file on its own via ./gatewaystart.sh within this environment and still got two windows, indicating that the issue lies within this file. The second window only opens after I finish the dual authentication on my phone after successfully logging in. This leaves me with an operational instance and one which is simply on the login screen. I am unsure what to do. Any insight or potential solutions is much appreciated . P.S Apologies for the briefness of my last post. I attempted to elaborate here as much as I can.