Server
From Resin 3.0
(Difference between revisions)
| (11 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Category:Configuration]] | + | [[Category: Cluster]] [[Category:Configuration]] |
| − | + | * See [[http://caucho.com/resin/doc/server-tags.xtp]] for the server tag documentation. | |
| − | + | A Resin '''server''' is a JVM instance which listens for HTTP requests and serves documents and servlets from a number of virtual hosts. | |
| − | + | Each server belongs to a [[cluster]] of identically-configured Resin instances that share load. The content configuration belongs to the [[cluster]] configuration, while the JVM and port configuration belongs to the server configuration. | |
| − | + | ||
| − | + | Multiple Resin servers are allowed on each machine. | |
| − | + | ||
| − | + | All Resin servers are managed by a [[watchdog]], which monitors the server health for reliability and manages the server's lifecycle. | |
| − | + | ||
| − | + | The <[[server]]> directive occurs in the <[[cluster]]> top-level directive. | |
| − | + | ||
| − | + | Multiple <[[server]]> directives are allowed as long as they have different <b>id</b> values. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 09:48, 14 January 2009
- See [[1]] for the server tag documentation.
A Resin server is a JVM instance which listens for HTTP requests and serves documents and servlets from a number of virtual hosts.
Each server belongs to a cluster of identically-configured Resin instances that share load. The content configuration belongs to the cluster configuration, while the JVM and port configuration belongs to the server configuration.
Multiple Resin servers are allowed on each machine.
All Resin servers are managed by a watchdog, which monitors the server health for reliability and manages the server's lifecycle.
The <server> directive occurs in the <cluster> top-level directive.
Multiple <server> directives are allowed as long as they have different id values.
