Enterprise Manager - Cluster Manager

Manage ColdFusion clusters and configure load balancing across instances

Overview

The Cluster Manager in ColdFusion Enterprise Manager provides centralized control over ColdFusion clusters, enabling you to group multiple server instances for load balancing, high availability, and simplified management. Clusters distribute incoming requests across member instances to improve performance, reliability, and scalability.

This page is available in ColdFusion Enterprise Edition (and in Trial and Developer editions) with the Server configuration. ColdFusion Standard does not support multiple instances or clusters.

Cluster Configuration

Essential settings for creating and configuring ColdFusion clusters.

Cluster Name

PurposeUnique identifier for the cluster
RequirementsMust be unique across all clusters in Enterprise Manager
RecommendationUse descriptive names that indicate purpose (e.g., production-web, api-cluster)
Best Practice: Use consistent naming conventions across your infrastructure. Include environment and purpose in cluster names (e.g., prod-web-cluster, dev-api-cluster).

Multicast Port

PurposeGroups the cluster members together. After you create a cluster, the port is written to cfusion/config/cluster.xml.
Default45564
RecommendationUse default unless port conflicts exist
FirewallEnsure multicast traffic is allowed between cluster members
Network Requirement: All cluster members must be on the same network segment with multicast enabled, or use sticky sessions without session replication.

Sticky Sessions

PurposeAfter a session is established on an instance, all future requests from that client are mapped to that instance. Disabling sticky sessions enables session replication.
RecommendationEnable for optimal performance unless full session replication is required
ImpactReduces session replication overhead and improves performance
Tradeoffs:
  • With Sticky Sessions: Better performance, but users lose session if their instance fails
  • Without Sticky Sessions: Full failover capability, but higher overhead from session replication

Adding Cluster Members

Configure server instances to join the cluster.

Instance Selection

PurposeChoose which ColdFusion instances to add to the cluster
RequirementsLocal instances from Instance Manager or registered remote instances. Each member must have the same applications deployed and the same resources configured (data sources, Solr collections, mappings). Local and remote members cannot share a JVM route.
RecommendationUse instances with similar hardware specifications for balanced load distribution
Best Practices:
  • Add at least 2 instances for high availability
  • Use 3+ instances for production clusters to handle member failures
  • Ensure all instances have identical application code and configurations
  • Test cluster failover before deploying to production

Load Balancing Configuration

Cluster Manager does not offer a choice of load-balancing algorithm. Load balancing is done by the web server connector: run the Web Server Configuration Tool (wsconfig) and point it at the cluster instead of a single server (the -cluster option on the command line). The connector alternates requests among the instances and switches requests to another instance when one stops running.

Relative weighting is set per instance, not in Cluster Manager: each instance has a load balancing factor that you edit in Instance Manager (or set when registering a remote instance). It applies only when the instance is in a cluster. Adobe's example: an instance with factor 2 receives twice as many requests as one with factor 1.

Session Management

Session Replication

PurposeReplicate session data across cluster members for failover
DefaultEnabled (when sticky sessions are disabled)
RecommendationDisable if using sticky sessions to reduce network overhead
ImpactIncreased network traffic and CPU usage, but provides seamless failover
Performance Impact: Session replication can significantly impact performance with large session data or high traffic. Consider storing minimal data in session scope.
Optimization Tips:
  • Keep session data small and simple (avoid storing large objects)
  • Use external session storage (Redis, database) for critical session data
  • Enable sticky sessions to reduce replication frequency
  • Monitor network bandwidth usage during peak traffic

Health Monitoring

Cluster Manager has no health check or auto-remove settings. Members find each other through Tomcat cluster membership on the multicast port. For a remote member, the Membership element in itsserver.xml cluster block sets this up; Adobe's sample block uses frequency="500"and dropTime="3000". The web server connector switches requests to another instance when one stops running.

Common Issues & Solutions

Cluster Members Not Communicating

Symptom: Instances appear in cluster but do not share session data or coordinate
Solutions:
  • Verify firewall allows multicast traffic on configured port
  • Ensure all cluster members are on same network segment
  • Check that multicast port is not in use by other applications
  • Verify network switches support multicast (IGMP snooping configured correctly)
  • Review ColdFusion logs for cluster communication errors

Unbalanced Load Distribution

Symptom: Some cluster members receive significantly more requests than others
Solutions:
  • Verify the connector was configured with wsconfig against the cluster, not a single instance
  • Ensure sticky sessions are configured correctly (check cookie/URL parameters)
  • Review web server connector configuration for proper worker definitions
  • Check that all cluster members are running
  • Check each instance's load balancing factor in Instance Manager

Session Loss After Instance Failure

Symptom: Users lose sessions when a cluster member fails
Solutions:
  • Verify session replication is enabled and functioning
  • Check that multicast communication is working between members
  • Enable Use J2EE session variables (Server Settings > Memory Variables) on every member instance; sticky sessions and session replication depend on it
  • Review session scope usage (Adobe notes that replication does not support arrays in session-scope CFCs or variables)
  • Consider external session storage (Redis, database) for critical applications
  • Test failover scenario in non-production environment

Related Resources

Enterprise Manager - Cluster Manager | ColdFusion Administrator | CFGuide