Server

From Resin 3.0

(Difference between revisions)
Jump to: navigation, search
 
(One intermediate revision by one user not shown)
Line 1: Line 1:
[[Category:Configuration]]
+
[[Category: Cluster]] [[Category:Configuration]]
  
The <[[server]]> directive occurs in the <[[resin]]> top-level directive. It allows any [[Environment]] configuration.
+
* See [[http://caucho.com/resin/doc/server-tags.xtp]] for the server tag documentation.
  
Multiple <[[server]]> directives are allowed as long as they have different <b>id</b> values.
+
A Resin '''server''' is a JVM instance which listens for HTTP requests and serves documents and servlets from a number of virtual hosts.
  
{| border="1"
+
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.
| directive || meaning || default
+
 
|-
+
Multiple Resin servers are allowed on each machine.
|[[Environment]] || Any [[Environment]] directive is allowed in the <server>
+
 
|-
+
All Resin servers are managed by a [[watchdog]], which monitors the server health for reliability and manages the server's lifecycle.
|[[Log Configuration|access-log]]||server-wide access log configuration
+
 
|-
+
The <[[server]]> directive occurs in the <[[cluster]]> top-level directive.
|[[Session Configuration|alternate-session-url-prefix]]||configures an alternate session rewriting prefix|none
+
 
|-
+
Multiple <[[server]]> directives are allowed as long as they have different <b>id</b> values.
|[[bind-ports-after-start]] || if true, only bind the HTTP ports after the hosts have completed initialization|false
+
|-
+
|[[cache]] || configures the [[Proxy Caching|Proxy Cache]] (Resin Professional only)
+
|-
+
|[[cluster|cluster]] || configures the server's cluster
+
|-
+
|&lt;connection-error-page> || error page to use when IIS cannot connect to Resin (3.0.19)
+
|-
+
|ear-default || default configuration for .ear files
+
|-
+
|enable-select-manager || enables the poll/select management of keepalive connections || false
+
|-
+
|environment-system-properties||[[environment]]-specific System.getProperties || true
+
|-
+
|error-page || server-wide error page configuration
+
|-
+
|[[http]]||configures a http port
+
|-
+
|[[host]]||configures a virtual host
+
|-
+
|host-default||configures default for all virtual hosts
+
|-
+
|host-deploy||configures a deployment directory for virtual host archives
+
|-
+
|id||unique identifier for the server|""
+
|-
+
|invocation-cache-size||size of the invocation cache||16k
+
|-
+
|invocation-cache-max-url-length||maximum length of a cacheable URL||1024
+
|-
+
|ignore-client-disconnect||if true, absorb [[ClientDisconnectException]]
+
|-
+
|keepalive-max||the maximum number of keepalive sockets
+
|-
+
|keepalive-timeout||maximum time a keepalive thread will wait for a new request
+
|-
+
|<[[persistent-store]]>||configures the persistent store
+
|-
+
|ping||configures relability checking (Resin Professional only)
+
|-
+
|[[port]]||configures a custom port listener
+
|-
+
|[[rewrite-dispatch]]|Dispatches requests based on the URL
+
|-
+
|root-directory||the root directory for the server||$SERVER_ROOT
+
|-
+
|[[Security Configuration|server-header]]||configures the value of the HTTP "Server:" header||Resin/3.0.x
+
|-
+
|[[Session Configuration|session-cookie]]||configures the servlet session cookie name||JSESSIONID
+
|-
+
|[[Session Configuration|ssl-session-cookie]]||configures the cookie to use for SSL connections||JSESSIONID
+
|-
+
|[[Session Configuration|session-url-prefix]]||configures the URL rewriting prefix||;jsessionid=
+
|-
+
|url-character-encoding||configures the character encoding of URLs||UTF-8
+
|-
+
|web-app-default||configures server-wide defaults for all web-apps
+
|}
+

Latest revision as of 02: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.

Personal tools