[BUG] Server powershell startup doesn't accept some Java 17 versions

[eddcomeau]

I swear this was working for me earlier and I don't see any changes, so I am wondering if I am missing something here. But I will document in case it is new

Describe the bug

The Windows PowerShell launcher incorrectly rejects a valid Java 17 executable supplied through OIE_JAVA_PATH or JAVA_HOME.

The issue is consistently reproducible when launching the development server with a valid Java 17 installation.

To Reproduce

1. Open PowerShell.

2. Navigate to the server setup directory:

   cd %location_of_engine%\engine\server\setup

3. Set a valid Java 17 executable:

   $env:OIE_JAVA_PATH = 'C:\Program Files\Eclipse Adoptium\jdk-17.0.18.8-hotspot\bin\java.exe'

4. Run the launcher:

   .\oieserver.ps1

5. Observe the validation error.

Expected behavior

The launcher should recognize the Java executable as valid and start the Open Integration Engine server.

Actual behavior

The launcher exits with:

'C:\Program Files\Eclipse Adoptium\jdk-17.0.18.8-hotspot\bin\java.exe'
is specified by the OIE_JAVA_PATH environment variable, which is not a valid
Java executable of at least version 17. Exiting.

The executable exists and successfully reports:

openjdk version "17.0.18"

Screenshots

Not applicable. The complete error is available in the PowerShell output.

Environment

• OS: Windows 10
• Shell: Windows PowerShell
• Java Distribution/Version: Eclipse Temurin OpenJDK 17.0.18
• Connect Version: Open Integration Engine 4.6.0
• Launcher: oieserver.ps1

Workaround(s)

Run the server through Gradle instead:

cd %location_of_engine%\engine
.\gradlew.bat :server:devRun --no-daemon