Hi, I discovered another strange and related behavior.
When leaving JETTY_HOST empty, instead of listening on all IPs (0.0.0.0 - IPv4 and IPv6), the server is listening on localhost (IPv4 127.0.0.1). I run some tests and I discovered that passing an empty jetty.host as param is different than not setting it. For example: ``` $ cd /usr/share/jetty/ $ java -jar start.jar [...] [main] INFO org.mortbay.log - Started SelectChannelConnector@0.0.0.0:8080 [CTRL+C] $ java -Djetty.host=0.0.0.0 -jar start.jar [...] [main] INFO org.mortbay.log - Started SelectChannelConnector@0.0.0.0:8080 [CTRL+C] $ java -Djetty.host= -jar start.jar [main] INFO org.mortbay.log - Started SelectChannelConnector@:8080 ``` And if we check netstat in the last case: ``` netstat -nlp | grep jsvc tcp6 0 0 127.0.0.1:8983 :::* LISTEN 24209/jsvc.exec ``` It is, if we pass `-Djetty.host=`, Jetty will listening on 127.0.0.1. This happens when JETTY_HOST is empty: ``` JAVA_OPTIONS="$JAVA_OPTIONS -Djava.io.tmpdir=$JETTY_TMP \ -DSTART=$JETTY_START_CONFIG \ -Djetty.home=$JETTY_HOME -Djetty.logs=$LOGDIR \ -Djetty.host=$JETTY_HOST -Djetty.port=$JETTY_PORT" ``` A good solution for this is always set JETTY_HOST and do NOT recommend the user to set it blank (as is done today). So, I'm proposing some changes to the /etc/default/jetty and /etc/init.d/jetty file. What do you think, guys? ** Patch added: "etc_initd_jetty.reachable.patch" https://bugs.launchpad.net/ubuntu/+source/jetty/+bug/1646202/+attachment/4786561/+files/etc_initd_jetty.reachable.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646202 Title: jetty init file prints wrong reachable information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jetty/+bug/1646202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
