Message-ID: <1415424064.298292.1368912580695.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_298291_944839026.1368912580695" ------=_Part_298291_944839026.1368912580695 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
You can start Jetty in such a way as to require identification before a = termination request is accepted. This can help safeguard against either acc= idental or malicious terminations.
This involves starting jetty with a STOP.PORT parameter= :
The STOP.PORT is the number of a port on which Jetty wi=
ll listen for termination requests. In this case, the port number is 8079. =
You can then stop jetty either with a
cntrl-c in the controlli=
ng terminal window (unless you have disassociated the Jetty process from a =
terminal), or by supplying this port number on a stop request from any term=
You can also supply a secret key on startup which must also be present o= n the termination request to enhance security:
WARNING: In some operating systems your STOP.KEY may be visible in the p= rocess list, allowing other users to connect to the stop port and initiate = the stop command. Please consider this before using the STOP.PORT and STOP.= KEY in start/stop scripts, for example init.d scripts on linux distribution= s.
As a further security measure, you can omit the STOP.KEY property on startup, in which case Jetty will generate and print on stdou= t a random key:
This key should then be supplied on the termination request: