RCPTT Runner produces misleading errors in a mismatched environment

[jochenberger]

I'm having trouble launching my AUT with recent versions.

The same app launches fine on Windows and Linux. Can you please advise on how I can debug this?

...
!ENTRY org.eclipse.pde.build 2 0 2025-12-10 15:28:20.374
!MESSAGE No default JRE installation selected

!ENTRY org.eclipse.pde.build 2 0 2025-12-10 15:28:20.375
!MESSAGE No default JRE installation selected

!ENTRY org.eclipse.rcptt.launching.ext 1 0 2025-12-10 15:28:20.551
!MESSAGE RCPTT: Launching AUT: AUT_0: Detected AUT architecture is x86_64. x86_64 arch detected

!ENTRY org.eclipse.rcptt.runner 1 0 2025-12-10 15:28:20.553
!MESSAGE AUT-0: Launch failed. Reason: Cannot locate JRE definition: "RCPTT JVM 1". Launch aborted.

!ENTRY org.eclipse.rcptt.runner 1 0 2025-12-10 15:28:20.553
!MESSAGE Failed to launch AUT:AUT-0: Launch failed. Reason: Cannot locate JRE definition: "RCPTT JVM 1". Launch aborted.

[basilevs]

• I expect more informative warnings to be printed above. Please attach more log.
• Run /usr/libexec/java_home -x to ensure that you have Java x86_64 installed.
• Double-check that AUT starts when launching manually, without RCPTT.
• Try using aarch64 build of your AUT to isolate architecture-dependent issues.
• Consider running Runner with assertions enabled, it will check integrity of selected JRE installation somewhat.
• Attach eclipse.ini (or product_name.ini) - it may reference JRE in a strange manner with a -vm argument.

My current hypothesis is that AUT has a bundled JRE of exotic packaging, and -vm argument in eclipse.ini is somehow malformed. RCPTT attempts to support all formats of that argument, but its handling logic is different from Eclipse launcher.

[jochenberger]

Yes, the app bundles a justj stripped 21 jre. I'll do some more checks tomorrow. Thanks for your help so far.

[jochenberger]

Setting -ea did not change anything unfortunately. Also, the logs do not contain any warnings regarding the JVM. The App launches fine when started manually.
The ini contains -vm /Users/user/aut/verinice.app/Contents/Eclipse/plugins/org.eclipse.justj.openjdk.hotspot.jre.full.stripped.macosx.x86_64_21.0.9.v20251105-0741/jre/bin/java.
I'll try to dig a little deeper.

[basilevs]

The ini contains -vm /Users/user/aut/verinice.app/Contents/Eclipse/plugins/org.eclipse.justj.openjdk.hotspot.jre.full.stripped.macosx.x86_64_21.0.9.v20251105-0741/jre/bin/java

INI files are supposed to contain relative path when pointing to embedded VM. Are you sure, this AUT works, when no system java is installed? Or when you run it as another user or from a different installation location?
Check is the file referenced exists and is executable (ls -l /Users/user/aut/verinice.app/Contents/Eclipse/plugins/org.eclipse.justj.openjdk.hotspot.jre.full.stripped.macosx.x86_64_21.0.9.v20251105-0741/jre/bin/java)

[jochenberger]

I changed -vm to a relative location, but that does not change anything. I'm getting the same messages.
Also, I'm also using absolute paths in Linux and Windows and that works fine.
Moreover, the same mechanism works when using a 2.5.5 runner snapshot.

[basilevs]

Are you sure that there is a line delimiter between -vm and filepath?

[jochenberger]

Yes. It says...

-startup
../Eclipse/plugins/org.eclipse.equinox.launcher_1.6.900.v20240613-2009.jar
--launcher.library
../Eclipse/plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.2.1100.v20240722-2106
-nl
de
-data
/Users/user/aut-workspace
-debug
-consolelog
-vm
../Eclipse/plugins/org.eclipse.justj.openjdk.hotspot.jre.full.stripped.macosx.x86_64_21.0.9.v20251105-0741/jre/bin/java
-vmargs
--add-opens=java.base/java.lang=ALL-UNNAMED
-Xms512m
-Xmx2048m
...

[jochenberger]

I captured the output from the erunner launch. In there, I see

...
Trying to use VM from application's ini file: /Users/user/aut/verinice.app/Contents/Eclipse/plugins/org.eclipse.justj.openjdk.hotspot.jre.full.stripped.macosx.x86_64_21.0.9.v20251105-0741/jre
AUT-0: Launch failed. Reason: Cannot locate JRE definition: "RCPTT JVM 1". Launch aborted.
...

On Linux, I get

...
Trying to use VM from application's ini file: /home/user/aut/verinice/plugins/org.eclipse.justj.openjdk.hotspot.jre.full.stripped.linux.x86_64_21.0.9.v20251105-0741/jre
Pass 1 (1) processed. 0 failed. spent: 0:09, 0:00 mins remaining. bp-screenshots. time: 8541ms 
Used memory: 113,3MB
...

[basilevs]

@jochenberger Please attach <runner_workspace>/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.jdt.launching.prefs

[jochenberger]

PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.runtime.name=OpenJDK Runtime Environment
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.runtime.version=21.0.9+10-LTS
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.specification.name=Java Platform API Specification
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.specification.version=21
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.version=21.0.9
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.vm.info=mixed mode, sharing
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.vm.name=OpenJDK 64-Bit Server VM
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.vm.version=21.0.9+10-LTS
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.os.arch=x86_64
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.sun.arch.data.model=64
eclipse.preferences.version=1
org.eclipse.jdt.launching.PREF_VM_XML=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<vmSettings defaultVM\="" defaultVMConnector\=""/>\n

[jochenberger]

FTR, on the Linux machine, the content is:

PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.runtime.name=OpenJDK Runtime Environment
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.runtime.version=21.0.9+10-LTS
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.specification.name=Java Platform API Specification
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.specification.version=21
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.version=21.0.9
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.vm.info=mixed mode, sharing
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.vm.name=OpenJDK 64-Bit Server VM
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.java.vm.version=21.0.9+10-LTS
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.os.arch=amd64
PREF_VM_INSTALL_SYSTEM_PROPERTY.org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType.RCPTT_JVM_1.sun.arch.data.model=64
eclipse.preferences.version=1
org.eclipse.jdt.launching.PREF_VM_XML=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<vmSettings defaultVM\="57,org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType13,1765524432840">\n    <vmType id\="org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType">\n        <vm id\="1765524432840" name\="jdk-21.0.9+10" path\="/data/jenkinsslave_2023/tools/hudson.model.JDK/java-21/jdk-21.0.9+10"/>\n        <vm id\="RCPTT_JVM_1" name\="RCPTT JVM 1" path\="home/user/aut/verinice/plugins/org.eclipse.justj.openjdk.hotspot.jre.full.stripped.linux.x86_64_21.0.9.v20251105-0741/jre"/>\n    </vmType>\n</vmSettings>\n

[basilevs]

Unable to reproduce. For now I will assume that relevant warnings are present in the omitted output. Java binary is likely non-executable.

[jochenberger]

The exact same AUT can be launched with 2.5.5.
I'll see if I can try other versions to see which one introduces the issue.

[basilevs]

The exact same AUT can be launched with 2.5.5. I'll see if I can try other versions to see which one introduces the issue.

I don't think this would help. Different versions of JDT launch VM in different manner, so the difference in behavior between minor releases is expected. Instead, please provide the Runner's and ls -l /Users/user/aut/verinice.app/Contents/Eclipse/plugins/org.eclipse.justj.openjdk.hotspot.jre.full.stripped.macosx.x86_64_21.0.9.v20251105-0741/jre/bin/java output.

Oh, and MCVE would be appreciated too, if you stumble upon one.