开云体育

Hi fran, Andy and ykrasik, do you have any news about this topic ? I am really interested about the same case ...

Hi!
I got it working fully on ARM32 by using Bellsoft's Full JRE 20 package. This is the only version I found it worked fully with.

Thanks for the suggestions. I played around with it some more and added those flags to any package I saw was giving a warning when accessing. However, that did not help with the display - I still see it as blue squares.

I still don't have an ARM64 with Linux, so I cannot try this myself.

You may be able to get a little farther (and make IBGW run more stable) by making the JVM11 look more like a JVM8 to TWS/IBGW. Java11 implements "Modules" with "Strong Encapsulation" so that access to resources between packages is much more restrictive than what Java 8 allows. You might find error messages in the early (unencrypted) logs or the console stderr where IBGW complains about something like:

• error: package XYZ is not visible
• java.lang.IllegalAccessError: class ABC cannot access class XYZ (in module SomeModule)

• or similar sounding messages

JVM11 and above provide command line options "-add-exports" and "--add-opens" that you can use to create the more permissive environment Java 8 based IBGW expects. "" explains how to do that.

Hope that helps,

闯ü谤驳别苍

开云体育

Cool. Thanks. Will try it today.

I got it working on ARM64. Posted it on github, relevant details are in this commit:

The UI doesn't work and shows up as a blue square, but I'm able to connect to it with my app and send trades.

Congratulations Andy, this is great. Would you mind telling us in better resolution how did you achieve this?

Cheers,
Frank

开云体育

Since I last wrote on this topic, last year, technology has moved forward and I am now pleased to report that IB Gateway will run on a Raspberry Pi 4B (4GB); a python client on the Pi reads in market data via the ib_insync package.
The install I used :
The stock PI OS 64 Bit 22 Sep 2022 Kernel 5.15 (Debian 11).
Bellsoft java jre11.0.17+7-linux-aarch64-full. (this includes the critical javafx libraries which the Gateway requires).
Gateway Ver 10.20 (copied over from a Linux Intel host).
The Pi was run up in headless mode over VNC.
It seems to work quite well under light load.

Andy

?

I last tried to do this a year ago on a Raspberry Pi 4B (4GB) running Ubuntu 21.04 64 bit.
The critical factor was obtaining a JVM with Javafx for this platform (Oracle dropped support for this after 8U6).
I tried various different JVMs, Bellsoft looked the most promising.?
I could run up Gateway, login to my paper account.? But was unable to get the settings dialog to appear (to configure ports etc).? The logs showed numerous UI errors, so Gateway was not happy.
Having spent too many hours on this I decided I had more pressing tasks and put the whole project on ice.
Doubtless a more determined effort could yield success.

Andy

Hello

Have you found a way to make it work? I tried different distros and always got to the same point of being unable to install IB Gateway. I installed IB Gateway in a Debian VM and copied the resulting folder but it didn't work either, not even installing Oracle's JDK1.8.0_321.

Wow, 闯ü谤驳别苍 this is outstanding work. The internet is a beautiful place thank you so much for taking the time to reply and explain the steps you took.

I don't use 2fa or tws so your experience gives me motivation for the gateway. I had seen a similar suggestion on stack overflow regarding adding the openfx paths to the Java exec. I had some hunches where to trial and error in the shell script so your results are time-saving.

I also saw another suggestion to do something like a symbolic link between the default-jre (/usr/bin) Java and openjfk ( /lib something I forget).

Can't wait to get back to the office and try these ideas out. Cheers and happy holidays.

My apologies for the confusion, Todd. As I said in my post, I only have an old 32bit Raspberry Pi 2 and was unable to make TWS/IBGW work on it. My next step would have been to grab a modern Pi 4, install a 64bit Debian distribution (instead of Raspbian) and try again with a 64bit JVM. It looked like 64bit ARM Java offerings were much more rich than 32bit ones. But you are correct, a 64bit JVM will not work on a 32bit OS.

Having said that, I went back to the drawing board and did some experiments on the Pi2 with 32bit OS and and 32bit JVMs. I installed the 32bit Linux versions of TWS and IBGW 981.3g and got pretty far, but not all the way. Here some thoughts that may help you:

• IBKR installation packages contain a Java JVM 1.8.0_152 with embedded JavaFX libraries. So the IBKR code relies upon pre-Java 9 rules related to access between classes from different origins and jars.
• Java 8 versions of JavaFX do exist for ARM 32bit, but they are missing some of the SWING related classes IBKR uses (such as JFXPanel).
• After Java 8, JavaFX became a separate set of modules and more stringent module access rules apply

With that background I did these steps:

• Download the stable Linux 32bit versions of IBGW and TWS. That is 981.3g right now
  
• Install the IBKR package with an ARM 32bit Java8 JVM:
  
  • app_java_home="path-to-arm-java-jre" sh ibgateway-stable-standaline-linux-x86.sh
  • The installation uses your ARM JRE (instead of the packaged x86 JRE) and JavaFX is not required at this stage
• Install a full featured JavaFX version that includes all SWING classes plus the corresponding JVM. After some experimenting I went with
  • openjfx-17.0.1_linux-arm32_bin-sdk.zip
  • OpenJDK17U-jdk_arm_linux_hotspot_17.0.1_12.tar.gz
• Small modification to the ibgateway script (in my case located in ~/Jts/ibgateway/981)
  • At the bottom at the two exec java statements insert right after ...bin/java"
  • --module-path path-to-your-javafx-installation/lib --add-modules=ALL-MODULE-PATH
  • They have to be located at the front of the command line options and adding them to the vmoptions file will not work
• Start IBGW with
  • app_java_home="path-to-your-java-JVM"? sh "~/Jts/ibgateway/981/ibgateway"
  • I had to do that as the root user since JavaFX tried to access all kinds of restricted devices related to mice, video, audio. But that could be an issue with my old Pi 2 and OS installation.
• The login dialogue comes up but I cannot get past the 2FA challenge (long story, but the only account I can use for the test needs this). All input works fine but IBGW claims that I had entered an incorrect security code (which I did not)
• launcher.log and the start script show a few exceptions related to module access restrictions to certain JavaFX classes. Most likely because of the more stringent module security enforced by the JVM. That can probably be worked around with proper module-info files, but will need some work and probably requires repackaging of IBKR JARs.
• Starting TWS 981.3g works with the same recipe. Logging into a demo account eventually hangs in "Processing startup parameters ..."

Hope this helps,
闯ü谤驳别苍

PS. Contact me directly if you want to work on this some more, since this the nitty gritty is probably too far out of scope for the group.

Hi 闯ü谤驳别苍?

Since the log4j upgrade requirement was announced I have been trying unsuccessfully to upgrade the gateway on the pi3b. I am going from 978 -> 981. I'm following the same steps I did before per Scott (MochaSatin) advice from above. Unfortunately, I'm seeing some JavaFX errors in the launcher logs as noted in another post.?

I'm using the default (default-jre) package from apt which appears to include OpenJDK-11 from the official raspbian/debian repository. I tried installing OpenJFX from APT as well, but there was no change in behavior in 981.?

I noticed you are saying to use the 64 Bit Oracle Java. Can you confirm how you are installing it and that you can use the 64 Bit Oracle Java on the Pi? My understanding is that the Pi OS is 32bit, so I'm confused why or how you would be installing the 64 bit version. Thanks

Thanks for your quick and clear response 闯ü谤驳别苍.? I'll follow your instructions and see how it goes.

You can get quite far very quickly with the stock installation for Intel x86 processors by doing four steps:

• Download the offline installer for a Linux TWS
• Install a decent Oracle 64bit Java JVM for ARM processors that must include JavaFX
• Install it with like this: app_java_home="/path/to/your/Java/installation" sh tws-latest-standalone-linux-x86.sh
  
• Use the "Start TWS" option from the last installation screen

I only have an old and very tired 32bit Raspberry Pi 2 with less than 800MB of RAM. It runs a 32bit version of Debian 10 (Buster) but does not meet many of the requirements for TWS,

However, TWS installation, startup, and login works fine. It hangs at "Starting Managers" but since TWS logs are encrypted at that point, debugging would be a challenge. A modern 64bit processor with good graphics might just work.

闯ü谤驳别苍