Jetty has moved!
Jetty is a project at the Eclipse Foundation.
Homepage:http://www.eclipse.org/jetty
Downloads: http://download.eclipse.org/jetty/
Documentation:http://www.eclipse.org/jetty/documentation/current/
About:http://www.eclipse.org/jetty/about.php
Jetty Powered:http://www.eclipse.org/jetty/powered/
Contact the core Jetty developers at www.webtide.com
private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Running Jetty-7.0.x

Running jetty7 is as simple as going to your jetty installation directory and typing:

This will start jetty and deploy a demo webapp available at:

Configuration

The part of the runline following -jar start.jar specifies the names of configuration files. These files instruct jetty which ports to listen on, which webapps to deploy, and generally configure all container-related customizable settings. You may have only one configuration file, or you may have multiple configuration files that mix in configuration or configure additional jetty instances. For example, to run jetty with the addition of an ssl connector and stdout/stderr redirected to a rolled over logged file, use the
command:

Options

Unlike Jetty-6, the start.jar of jetty-7 does not automatically put all the libraris in lib onto the classpath.
Optional components of Jetty can be included with the -DOPTION parameter. For example to run jetty with JMX:

Standard options include:

jetty

always

jsp

default

ssl

default

plus

 

annotations

 

wadi

 

grizzly

 

jmx

 

xbean

 

Deploying web applications

In order to deploy a new webapp, you need not do anything more than drop your war file or unpacked war file into the webapps directory. See also the ContextDeployer and WebAppDeployer pages for more options.

Stopping

Apart from stopping jetty with a cntrl-c in the same terminal window as you started it, you can
start Jetty so that it listens on a local port for stop commands:

The server can then be stopped using a different terminal window on the same machine:

If the STOP.KEY property is ommitted from the start command, then a random key is printed on standard out. If the STOP.PORT is set to 0, a random available port is assigned and printed on stdout.

See also Securing Jetty.

  • No labels
Contact the core Jetty developers at www.webtide.com
private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery