Tom Sawyer server, Java installation check failed

Bug Reports Modeler
1

Hello SysIDE community,

I did some changes to my JDK trying to set up a sysmlv2 local server and now the visualizer is not starting:

image
image1370×642 55.8 KB

does anyone has had a similar issue?

My current java -version is:

java -version

/opt/homebrew/Cellar/openjdk/24.0.2/libexec/openjdk.jdk/Contents/Home
openjdk version “24.0.2” 2025-07-15
OpenJDK Runtime Environment Homebrew (build 24.0.2)
OpenJDK 64-Bit Server VM Homebrew (build 24.0.2, mixed mode, sharing)

Many thanks in advance and best regards!

2

Hi Alejandro,

Thanks for reaching out with your issue.

Could you please send us (syside.support@sensmetry.com) the Modeler logs so that we can better understand the cause. You can find instructions on how to obtain them in our docs Troubleshooting section.

Also, problem could be coming from the wrong java path in SysIDE settings. Could check if the path is correct and send us the value of that setting together with your logs?

To find the path:

  • go to VS Code settings
  • find Syside › Modeler › Viz Tom Sawyer: Java setting.

If you have any more questions, please don’t hesitate to ask.

Best regards,

Simas

1 Like
3

Hello,

thanks to Simas support I was able to solve this issue. I let the solution below in case someone faces a similar situation at some point.

So the problem was that (due to the changes I did to JDK) the VSCODE SysIDE settings for Tom Sawyer was pointed to an old version of java:

image
image2270×768 178 KB

changing this parameter to the new path actually solved the ‘Java installation check failed’:
/opt/homebrew/Cellar/openjdk/24.0.2/libexec/openjdk.jdk/Contents/Home/bin/java

image
image1400×580 49.8 KB

I have changed this parameter both in 'User‘ and 'Workspace‘.

2 Likes
4

Hi Alejandro and anyone else stumbling on the thread!

Just a quick note about workspace settings. These settings get saved to a .vscode folder within your working directory and can be tracked by Git (unless explicitly told not to in .gitignore).

This means that workspace settings are better suited for team-wide settings (e.g. Syside > Line Length to enforce consistent formatting across the team, or Syside › Modeler: Tools Version to specify that this project for some reason chose to use an older version of SysIDE).

On the other hand, Java (and Python) path is very user-specific. Your teammates working on the same project might not have a homebrew folder on their machine or 24.0.2 version of OpenJDK, and thus their Modeler would fail to start as the Java binary cannot be found in the path supplied. Thus, I would recommend setting the path to Java only in your user settings.

This might not be an issue if you are working on the project alone, but it is always good to start forming good habits from early on, so that when others join you in your SysIDE adventure, you do not get any nasty configuration surprises.

Hope this helps and Thank You for using SysIDE!

– Simonas