IBC doesn't work with latest 1048 version of IBGW

[pps83]

Here's the log output:

+==============================================================================
+
+ IBC version 3.24.0
+
+ Running GATEWAY 1048 at 29-Jul-26 18:51:25.68
+
+ Diagnostic information is logged in:
+
+ C:\IBC\Logs\IBC-3.24.0_GATEWAY-1048_WEDNESDAY.txt
+
+
+ ** Caution: closing this window will close GATEWAY 1048 **
+ (window will close automatically when you exit from GATEWAY 1048)
+
+==============================================================================
+
+                       **** An error has occurred ****
+
+ Error while: Running StartIBC.bat
+
+ ERRORLEVEL = 1001
+
+ Please look in the diagnostics file mentioned above for further information
+
+==============================================================================
+
+ Press any key to close this window

Note, the same config works with 1047, but fails with updated 1048. I tested it and confirmed the issue another machine.
AI says that IBGW screw up their installer, yet, if I run ibgw directly then it work with no issues.

[rlktradewright]

Thanks for that. I'll look into it shortly.

Errorlevel 1001 means that no Java runtime was found by the script, so it may be that the installer has put some file(s) in a different location that the script is not expecting.

[pps83]

This fixes it: pps83@5776858
The alternative repair is to rewrite 1048's inst_jre.cfg to a valid path

[smithlk7-maker]

We're also gated by this — our containerized Gateway deployment (gnzsnz/ib-gateway based) is pinned below 10.48 solely because of this launch failure. Since a new release is imminent (per #377), would you consider including the fix from pps83/IBC@5776858 (linked above) — or an equivalent inst_jre.cfg path repair — in it? With IBC winding down, this is the one remaining blocker for running current Gateway builds under IBC. Thank you for all the years of work on this project.

[rlktradewright]

I'm very much aware of this issue, and I now have an IBC version that deals with it properly. I've been trying to get to a position of doing a new release for a week or two now, but it's been a struggle for various reasons which I don't need to elaborate on.

Please be patient. I will deliver a new version that handles this issue and a good many others as soon as I can, before I leave the project.

Can I just say though that you seriously need to have a plan in place for what you're going to do post-IBC. Just because I release a version that clears all currently outstanding issues doesn't mean you're safe and dry for anything other than the short term. IBKR could release a TWS/Gateway version that blows IBC out of the water at any time..

[rlktradewright]

Fixed in commit 80cb002