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 for sponsored feature development
By default, Jetty will instantiate a single instance of the
HouseKeeper at startup with default settings.
The default settings are:
JETTY_WORKER_INSTANCEenvironment variable, or
node0if the environment value is not set. If you have more than one Jetty instance, it is crucial that you explicitly configure the worker name on each Jetty instance (see below for how to configure).
maxInactiveIntervalof your sessions to ensure that they are promptly scavenged. See below for instructions on how to configure this.
This will enable the
$jetty.home/etc/sessions/id-manager.xml file and generate a
id-manager.xml file instantiates a single
HouseKeeper and configures them using the properties from the
Edit the ini file to change the properties to easily customize the
node1. This uniquely identifies the Jetty server instance within a cluster. If you have more than one Jetty instance, it is crucial that you configure the worker name differently on each jetty instance.