jetty.project icon indicating copy to clipboard operation
jetty.project copied to clipboard

stop.host property always uses the default 127.0.0.1

Open sweco-nltbim opened this issue 5 months ago • 2 comments
trafficstars

Jetty version(s) 12.0.19 12.0.20 12.0.22

Jetty Environment ee8

Java version/vendor (use: java -version) openjdk version "17.0.13" 2024-10-15 OpenJDK Runtime Environment Temurin-17.0.13+11 (build 17.0.13+11) OpenJDK 64-Bit Server VM Temurin-17.0.13+11 (build 17.0.13+11, mixed mode, sharing)

OS type/version Ubuntu 24.04.1 LTS

Description According to the documentation I am able to change certain properties to stop Jetty remotely.

Image

Unfortunately, stop.host property is not being set correctly when Jetty is starting up. It always uses the default 127.0.0.1

I am currently running Jetty in a container in Kubernetes.

How to reproduce? I enabled the following modules in Jetty:

server,http,ee8-deploy,ee8-jsp,jvm,forwarded,logging-jetty

I passed the --dry-run command to verify if the stop.host is set correctly using:

java -jar $JETTY_HOME/start.jar --dry-run stop.host=0.0.0.0 stop.port=9090 stop.key=jetty

This resulted in the following (you can clearly see stop.host is being ignored):

Image

sweco-nltbim avatar Jun 12 '25 10:06 sweco-nltbim