Starting with Jetty 7.6.9 the STOP.KEY is no longer generated and displayed (instead it defaults to "eclipse").
Starting with Jetty 7.6.9 the STOP.PORT is ignored unless the stopAtShutdown option is set using the following:
This was not previously necessary.
I would like to see the behaviour go back to what it has been with all releases previous to 7.6.9, where I could simply specify a STOP.PORT and have the engine listen on that port and generate a "secure" STOP.KEY. Currently it seems I must provide a STOP.KEY on the command-line which is visible to all users of the system.
Re: Jetty 7.6.9: STOP.PORT & STOP.KEY behavior has changed
It should be noted that the arguments within the "start.ini" file override the command line arguments. This can catch you out if you are using the start.ini to provide arguments when starting a few instances and then try to stop one using the appropriate arguments via the command line.