javaApplicationStub crash

[matt_k]

Hi there
I seem to be have the same issue as detailed in this common-problems/topic681.html but with version 27.0 on Mac OSX 13.7.3, which I installed last week.
I checked the folder /System/Library/Frameworks/JavaVM.framework/Versions/A/Resources but the MacOS folder was missing and so there was no JavaApplicationStub file to copy to the oxygen.app/Contents/MacOS folder. When I checked, it is already present in the oxygen.app/Contents/MacOS.
I just tried the java version command in Terminal and got this:

Error: Could not find or load main class version
Caused by: java.lang.ClassNotFoundException: version

I only recently installed graalvm-jdk-23.0.1+11.1 as recommended in another post relating running older DITA-OT. It is still in the /Library/Java/JavaVirtualMachines folder.
Has something gone wrong during the install of Oxgyen 27.0?
Many thanks
Matt

[adrian]

Hello,

The forum topic you indicated is from 20+ years ago. It's unlikely your crash has anything in common with that (other than that it's a crash). Don't try to apply old workarounds on new versions as they are very likely to completely break the app.

Oxygen doesn't currently (v27) support Java 21+. It's possible to run it with v21, but we haven't tested 22 or later and only plan to support LTS versions of Java. graalVM brings other possible complications to the table. Try to stick to Java SE or OpenJDK distributions.
Try using a standard distribution of Oxygen as it already bundles the appropriate Java VM.
If you need to run DITA-OT with a newer version of Java, configure the JavaVM only for the DITA-OT in the transformation scenario dialog.

Regards,
Adrian

[matt_k]

Thanks for the prompt reply Adrian.
I installed GraalVM because of the error messages I got when transforming using our DITA-OT 3.2.1 plugins. I realise that is now very old, but we are not in a position to change to a newer version OT at present.
I have uninstalled GraalVM now, but Oxygen is still not launching. I suspect that is because I changed the Java home path when I installed GraalVM.
How can I get Oxygen to use the bundled Java VM again?

[matt_k]

I have managed to get Oxygen to open again, after reinstalling it (again).
I'm still having issues running our custom plugins with DITA-OT 3.2.1 and have now installed Java 1.8 on my mac and adjusted the transform scenario accordingly. But, it still didn't work.
I restarted Oxygen and now I'm getting a completely different error:

FileNotFoundException-/Users/XXX/Downloads/xxxxxditamap-bundle/learningbookmap.dtd (No such file or directory)

[Radu]

Hi,
If you get that specific error when validating a DITA XML topic, you should go to the Oxygen Preferences->"DITA" page and change the default used DITA OT to be your custom DITA OT installation folder.
You should also install the plugins in the custom DITA OT if you have not yet done so.
https://www.oxygenxml.com/doc/versions/ ... tor-2.html
Regards,
Radu

[matt_k]

Hi Radu
I think I have resolved it now. I found that you have to select the DITA-OT by navigating to the directory where it is located, rather than select from the drop-down list which has all previously used toolkits.
Similarly, I found that I needed to reselect the ditaval file, rather than pick from the the drop-down list of previously used ditavals.
I have also checked our server transform log to see what version of Java is used there and have installed the same version on my Mac.
I shall have to remember to go through this process every time I upgrade Oxygen.
Many thanks
Regards
Matt

[matt_k]

I spoke too soon.
I have just tried to open Oxygen (first time since yesterday) and have got the same javaApplicationStub crash.
Java is definitely installed:

openjdk version "11.0.26" 2025-01-21
OpenJDK Runtime Environment Temurin-11.0.26+4 (build 11.0.26+4)
OpenJDK 64-Bit Server VM Temurin-11.0.26+4 (build 11.0.26+4, mixed mode)

[adrian]

Hi,

The macOS (dmg) distribution of Oxygen is not using your installed Java to run, it has its own Java bundle, OpenJDK Runtime Environment Temurin-17 in its installation folder.
If the issue persists try to restart your system. If you haven't tampered with any of Oxygen's files and it started to fail after a day, there may be an issue with the system. If you did tamper with it, try to install it again. Pick Replace, do not use Merge if installing on top of an existing version of Oxygen.

Regards,
Adrian

[matt_k]

Hi Adrian
Thanks for the reply.
The only thing I did to modify the Oxygen installation was to add a plugin to /Applications/Oxygen XML Editor/plugins.
The plugin is designed to allow us to open DITA files from our CCMS in Oxygen via WebDav.
I reinstalled Oxygen and did not install the plugin this time and Oxygen opens fine now. I also removed the other version of Java from /Library.
I will let our CCMS vendor know that the plugin is not working with the current version of Oxygen.
Thanks again for your help.
Regards
Matt

[adrian]

Hi,

Make sure your plugin is compatible with the version of Oxygen you are using.

How is the plugin deployed? Does the plugin deployment involve running a .sh script?
We know of some old third-party Oxygen plugins that have a sh script that makes changes to the Info.plist file of the Oxygen app. While that worked for older versions of Oxygen and macOS, making changes to the Info.plist file nowadays renders the app unusable (.app signature no longer checks and macOS refuses to start it).

Regards,
Adrian