Page History
...
Release 2.5.0 ships with Jetty 11 and requires a Java 11 JRE/JDK., see Jira server SOS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1367
Changes in Jetty 11 affect the location of settings:
...
The settings are the same, however, their location in individual *.ini files in the start.d
sub-directory is different:
*.ini File | Modules | Settings |
---|---|---|
console-capture.ini | --module=console-capture | jetty.console-capture.* |
deploy.ini | --module=deploy | jetty.deploy.* |
ext.ini | --module ext | |
http.ini | --module http | jetty.http.* |
https.ini | --module https | |
resources.ini | --module=resources | |
rewrite.ini | --module=rewrite | jetty.rewrite.* |
ssl.ini | --module=ssl | jetty.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.
...
JETTY_BASE/start.d/ssl.ini
: this file includes settings for JOC Cockpit's HTTPS port (jetty.ssl.host, jetty.ssl.port
) and 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
: this file includes settings for JOC Cockpit's HTTP port (jetty.http.host, jetty.http.port
). Settings in this file enable/disable the HTTP module.
Users who make use of Docker container 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.
...