An error pop-up notification "Error getting java version for : 'java -version' output was unable to be parsed." is shown at extension startup. It does not happen consistently though.
Closer investigation (debugging) revealed that the issue happens due to a race condition in checkJavaVersion function in requirements.ts. cp.execFile() callback is executed after process.on('exit') callback in the problem situation. According to child_process documentation, this can be considered as expected behavior:
When the 'exit' event is triggered, child process stdio streams might still be open.
An error pop-up notification "Error getting java version for : 'java -version' output was unable to be parsed." is shown at extension startup. It does not happen consistently though. Closer investigation (debugging) revealed that the issue happens due to a race condition in checkJavaVersion function in requirements.ts. cp.execFile() callback is executed after process.on('exit') callback in the problem situation. According to child_process documentation, this can be considered as expected behavior:
See https://github.com/redhat-developer/rsp-server-community/issues/185