Clustering

From Resin 3.0

Revision as of 08:23, 7 December 2011 by Pcowan (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
40px-Edit-clear.png This article requires cleanup and may refer to a legacy version of Resin.

Please visit http://www.caucho.com/documentation/ for the most up-to-date documentation.

A Cluster is a collection of Resin JVMs all running the same application. The <cluster> directive configures the cluster.

See Also

Selecting a Backend Server

In testing situations, it can be important to select a particular backend server when making a request of the front-end server. The easiest solution is to take advantage of sticky sessions and use the ";jsessionid=" url.

Supposed in the following cluster of three backend servers, you wanted to test the second one, i.e. the one listening to 192.168.0.11. You could send a request to "/test.jsp;jsessionid=bXXXX".

resin.xml

<resin xmlns="http://caucho.com/ns/resin">
   ...
  <cluster>
    <server id="a" address="192.168.0.10" port="6800"/>
    <server id="b" address="192.168.0.11" port="6801"/>
    <server id="c" address="192.168.0.12" port="6802"/>
     ...
   </cluster>
 </resin>

The 'b' will select the second server. Because that request uses URL rewriting and also because "bXXXX" value is too short, Resin will generate a new session instead of using the cookie value of "bXXXX".

Note, the non-reuse of the session value "bXXXX" is affected by the <reuse-session-id> configuration.

Personal tools