Worker doesn't start with new build of AdoptOpenJDK 11 Hotspot

Assignee

Pavel Salamon

Reporter

Alexej Vetusko(Deactivated)

Labels

Bluereadyrelease-notes

Sprint

None

Description

With the AdoptOpenJDK jdk-11.0.12+7 version, Worker failed to start complaining about PrintGCDateStamps java option.

The workaround is to add -verbose:gc to jvm arguments of the worker.

Steps to reproduce

None

Attachments

30 Aug 2021, 04:38 PM
13 Aug 2021, 09:15 AM

Activity

Show:

Filip Vaško August 16, 2021 at 7:56 AM
Edited

Testing.
:check_mark: reproduced on the released 5.8.2, 5.9.1 and 5.10.1 - worker does not start on AdoptOpenJDK 11.0.12+7
:check_mark: worker starts successfully on release-5-8-3 #1, release-5-9-2 #1 and release-5-10-2 #1 on AdoptOpenJDK 11.0.12+7
:check_mark: tried to run a few graphs and jobflows - they were successfully executed on worker

Closing.

Pavel Salamon August 12, 2021 at 10:45 AM

Improved jvm detection from https://cloverdx.atlassian.net/browse/CLO-21089#icft=CLO-21089 has been backported to 5.8 and then merged to 5.9 and 5.10.

Pavel Salamon August 12, 2021 at 8:22 AM

New builds of AdoptOpenJdk changed java.vendor property from "AdoptOpenJdk" to "Eclipse Foundation". This broke jvm detection in clover versions prior to 5.11.

In 5.11 and newer, this is not an issue - we improved jvm detection in https://cloverdx.atlassian.net/browse/CLO-21089#icft=CLO-21089, so it works for new AdoptOpenJdk builds as well.