Note: The Cluster Manager discussed in this article is a feature only available when running ColdFusion MX 7 in a multiserver configuration. This is available when choosing Option 2 at the beginning of the installation process.

Sticky sessions can be enabled or disabled in the Cluster Manager in the ColdFusion MX 7 Administrator. Sticky sessions cause requests to be directed to the same server once a session is established.

In order for changes to the Sticky Session setting to take effect, each server in the cluster as well as the webserver must be restarted. It is best to do this in the following order:

  1. Enable or disable Sticky Sessions in the Cluster Manager and click the Submit button.
  2. Stop each server in the cluster and the webserver. If using IIS, stop the World Wide Web Publishing Service. (It is not sufficient to just click the Stop icon in the Microsoft Management Console).
  3. Start each server in the cluster. This may be done using the Instance Manager in the ColdFusion MX 7 Administrator, or from a command line.
  4. Start the webserver.

Additional Information

Sticky sessions are maintained by pre-pending the server.id to the jsessionid. The server.id is defined in the /SERVER-INF/connector.properties file located under the root of each server. For example, C:\JRun4\servers\CFMX7_1\SERVER-INF\connector.properties. This is why it is necessary to enable J2EE Sessions for sticky sessions to work. The webserver must be restarted so that the connector is able to read the server.id properly after sticky sessions are enabled.

It is recommended you install the latest updates to JRun and ColdFusion MX when working with clusters.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy