RFR: 8352533: Report useful IOExceptions when jspawnhelper fails

[Dan Lutker]

On Tue, 25 Mar 2025 19:38:27 GMT, Aleksey Shipilev <shade at openjdk.org> wrote:

>> src/java.base/unix/native/libjava/ProcessImpl_md.c line 324:
>> 
>>> 322: #define SPAWN_HELPER_INTERNAL_ERROR_MSG "\n" \
>>> 323:   "Possible reasons:\n" \
>>> 324:   "  - Spawn helper ran into JDK version or configuration problems\n" \
>> 
>> Can we be clear and say "Spawn helper ran into a mismatch between the running JDK and the version on disk" or something similar?
>
> We don't know the exact reason for jspawnhelper failure, so that would be a bad message that might push users to wrong resolution path. Instead, like `vmError`, we list most frequent possibilities and let users follow-up.

I just want to point uses to know what the root cause might be and not have to reach out through support channels.
Does "Spawn helper ran into JDK version mismatch or configuration problems" seem better to you?

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/24149#discussion_r2012822013