Skip to end of metadata
Go to start of metadata

Introduction

Release 2.5.0 ships with Jetty 11 and requires a Java 11 JRE/JDK, see JOC-1367 - Getting 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
    • JETTY_BASE/start.ini
  • Starting from Release 2.5.0 Jetty 11 is used that expects settings from a number of configuration files in the directory:
    • JETTY_BASE/start.d/*.ini

The settings are the same, however, their location in individual *.ini files in the start.d sub-directory is different:

*.ini FileModulesSettings
console-capture.ini--module=console-capturejetty.console-capture.*
deploy.ini--module=deployjetty.deploy.*
ext.ini--module ext
http.ini--module httpjetty.http.*
https.ini--module https
resources.ini--module=resources
rewrite.ini--module=rewritejetty.rewrite.*
ssl.ini--module=ssljetty.ssl.*
jetty.sslContext.*

Migration

The JOC Cockpit installer will migrate existing settings from the start.ini file to individual files in the start.d directory.

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.

  • No labels