Details
Description
In the latest init.d script for the Artifactory service control, there is this new function introduced:
checkJavaVersion()
Unfortunately what it does is checking the for Java first in the path and then in the artDefaultFile, and if there is a Java in the path (there usually is - the default system one) it is considered as the Java to be used, and the init script complains it's an old version.
After commenting it out from the start) and wait) cases, it is skipped and Artifactory starts successfully with the correct Java configured in the artDefaultFile.
The check should first care for the configured Java, and then fall back to the one available in the path.
Attachments
Issue Links
- is duplicated by
-
RTFACT-8583 Linux service script ignores JAVA_HOME when default JAVA is found
-
- Resolved
-