By default the jetty-runner will listen on port 8080. You can easily change this on the command line using the --port command. Here’s an example that runs our simple.war on port 9090:

> java -jar jetty-runner.jar --port 9090 simple.war

Instead of, or in addition to, using command line switches, you can use one or more jetty.xml files to configure the environment for your webapps. Here’s an example where we apply two different jetty.xml files:

> java -jar jetty-runner.jar --config jetty.xml --config jetty-https.xml simple.war

Print out the version of Jetty and then exit immediately.

> java -jar jetty-runner.jar --version

Cause Jetty to write a request log with the given name. If the file is prefixed with yyyy_mm_dd then the file will be automatically rolled over. Note that for finer grained configuration of the request log, you will need to use a Jetty xml file instead.

> java -jar jetty-runner.jar --log yyyy_mm_dd-requests.log  my.war

Redirect the output of jetty logging to the named file. If the file is prefixed with yyyy_mm_dd then the file will be automatically rolled over.

> java -jar jetty-runner.jar --out yyyy_mm_dd-output.log my.war

Like Jetty standalone, the default is for the connectors to listen on all interfaces on a machine. You can control that by specifying the name or ip address of the particular interface you wish to use with the --host argument:

> java -jar jetty-runner.jar --host 192.168.22.19 my.war

The default port number is 8080. To configure a https connector, use a Jetty xml config file instead.

> java -jar jetty-runner.jar --port 9090  my.war

You can configure a port number for jetty to listen on for a stop command, so you are able to stop it from a different terminal. This requires the use of a "secret" key, to prevent malicious or accidental termination. Use the --stop-port and --stop-key parameters as arguments to the jetty-runner:

> java -jar jetty-runner.jar --stop-port 8181 --stop-key abc123

Then, to stop Jetty from a different terminal, you need to supply the same port and key information. For this you’ll either need a local installation of Jetty, the jetty-maven-plugin, the jetty-ant plugin, or a custom class. Here’s how to use a Jetty installation to perform a stop:

> java -jar start.jar --stop-port 8181 --stop-key abc123 --stop

With a local installation of Jetty, you add jars and classes to the container’s classpath by putting them in the {$jetty.base}/lib directory. With the jetty-runner, you can use the --lib, --jar and --classes arguments instead to achieve the same thing.

--lib adds the location of a directory which contains jars to add to the container classpath. You can add 1 or more. Here’s an example of configuring 2 directories:

> java -jar jetty-runner.jar --lib /usr/local/external/lib --lib $HOME/external-other/lib my.war

--jar adds a single jar file to the container classpath. You can add 1 or more. Here’s an example of configuring 3 extra jars:

> java -jar jetty-runner.jar --jar /opt/stuff/jars/jar1.jar --jar $HOME/jars/jar2.jar --jar /usr/local/proj/jars/jar3.jar  my.war

--classes add the location of a directory containing classes to add to the container classpath. You can add 1 or more. Here’s an example of configuring a single extra classes dir:

> java -jar jetty-runner.jar --classes /opt/stuff/classes my.war

If statistics gathering is enabled, then they are viewable by surfing to the context /stats. You may optionally protect access to that context with a password. Here’s an example of enabling statistics, with no password protection:

> java -jar jetty-runner.jar --stats unsecure my.war

If we wished to protect access to the /stats context, we would provide the location of a Jetty realm configuration file containing authentication and authorization information. For example, we could use the following example realm file from the Jetty distribution:

jetty: MD5:164c88b302622e17050af52c89945d44,user
admin: CRYPT:adpexzg3FUZAk,server-administrator,content-administrator,admin
other: OBF:1xmk1w261u9r1w1c1xmq,user
plain: plain,user
user: password,user
# This entry is for digest auth.  The credential is a MD5 hash of username:realmname:password
digest: MD5:6e120743ad67abfbc385bc2bb754e297,user

Assuming we’ve copied it into the local directory, we would apply it like so

> java -jar jetty-runner.jar --stats realm.properties my.war

After navigating to http://localhost:8080/ a few times, we can point to the stats servlet on http://localhost:8080/stats to see the output:

Statistics:
Statistics gathering started 1490627ms ago

Requests:
Total requests: 9
Active requests: 1
Max active requests: 1
Total requests time: 63
Mean request time: 7.875
Max request time: 26
Request time standard deviation: 8.349764752888037


Dispatches:
Total dispatched: 9
Active dispatched: 1
Max active dispatched: 1
Total dispatched time: 63
Mean dispatched time: 7.875
Max dispatched time: 26
Dispatched time standard deviation: 8.349764752888037
Total requests suspended: 0
Total requests expired: 0
Total requests resumed: 0


Responses:
1xx responses: 0
2xx responses: 7
3xx responses: 1
4xx responses: 0
5xx responses: 0
Bytes sent total: 1453


Connections:
org.eclipse.jetty.server.ServerConnector@203822411
Protocols:http/1.1
Statistics gathering started 1490606ms ago
Total connections: 7
Current connections open: 1
Max concurrent connections open: 2
Total connections duration: 72883
Mean connection duration: 12147.166666666666
Max connection duration: 65591
Connection duration standard deviation: 23912.40292977684
Total messages in: 7
Total messages out: 7


Memory:
Heap memory usage: 49194840 bytes
Non-heap memory usage: 12611696 bytes