Release 2.5.0 ships with Jetty 11 and requires a Java 11 JRE/JDK, see - JOC-1367Getting issue details... STATUS
Changes in Jetty 11 affect the location of settings:
- Up to Release 2.4.1 Jetty 9 is used that expects settings from a single configuration file
- Starting from Release 2.5.0 Jetty 11 is used that expects settings from a number of configuration files in the directory:
The settings are the same, however, their location in individual *.ini files in the
start.d sub-directory is different:
The JOC Cockpit installer will migrate existing settings from the
start.ini file to individual files in the
Users who make use of JS7 - JOC Cockpit HTTPS Connections should check that relevant settings are now in place in the following configuration files:
JETTY_BASE/start.d/ssl.ini: this file includes settings for access to the Java keystore and truststore.
JETTY_BASE/start.d/https.ini: settings in this file enable the HTTPS module.
JETTY_BASE/start.d/http.ini: settings in this file enable/disable the HTTP module.
Users who make use of Docker images and therefore do not run the JOC Cockpit installer should double-check that the
start.d folder and related files are created by the entrypoint script during container start-up.