Hostelements inside the Engine element; each
Hostelement represents one virtual host. You need to define at least one
Hostelement and one of the Hosts must have a name that matches the defaultHost value defined in the parent Engine element.
Engineelement can contain at most one
Realmelement represents a database of users and their roles: the user information defined in the respective resource is shared across all Hosts and Contexts nested inside the Engine. Realm setting in the Engine element can be overridden by another
Realmelement defined in a lower-level element; that is, a Host or Context element.
Table 4.5. Engine Element Attributes
delay between the invocation of the
If set to a positive value, the engine produces a thread. The thread waits for the specified amount of time and then invokes the
Host and Context containers can also define the backgroundProcessorDelay attribute. If the delay of a child container is not negative, the child container is using its own processing thread.
class implementing the Engine
The class must implement the org.apache.catalina.Engine interface. If not specified, the standard value
name of the default host name
The default Host processes requests directed to host names on the server that are not configured in the
identifier used in load balancing scenarios to enable session affinity (so-called "sticky sessions")
The identifier must be unique across all JBoss Web servers which participate in the cluster. It is appended to the generated session identifier so that a front-end proxy can always forward a particular session to the same JBoss Web instance.
logical name of the Engine used in log and error messages
When using multiple Service elements in the same Server, each Engine must be assigned a unique name.
Engineelement are ignored.