Specifying a Timeout Value For RMIs Configure Server Affinity for Distributed JMS Destinations Configuring Load Balancers that Support Passive Cookie Persistence

10-10 Using Clusters for Oracle WebLogic Server

8. Click Save to save your changes.

9. Click Activate Changes in the top left corner once you are ready to activate your

changes.

10.2.6 Specifying a Timeout Value For RMIs

You can enable a timeout option when making calls to the ReplicationManager by setting the ReplicationTimeoutEnabled in the ClusterMBean to true. The timeout value is equal to the multicast heartbeat timeout. Although you can customize the multicast timeout value, the ReplicationManager timeout cannot be changed. This restriction exists because the ReplicationManager timeout does not affect cluster membership. A missing multicast heartbeat causes the member to be removed from the cluster and the timed out ReplicationManager call will choose a new secondary server to connect to.

10.2.7 Configure Server Affinity for Distributed JMS Destinations

To understand the server affinity support provided by WebLogic Server for JMS, see Section 5.3, Load Balancing for JMS.

10.2.8 Configuring Load Balancers that Support Passive Cookie Persistence

Load balancers that support passive cookie persistence can use information from the WebLogic Server session cookie to associate a client with the WebLogic Server instance that hosts the session. The session cookie contains a string that the load balancer uses to identify the primary server instance for the session. For a discussion of external load balancers, session cookie persistence, and the WebLogic Server session cookie, see Section 5.1.2, Load Balancing HTTP Sessions with an External Load Balancer. To configure the load balancer to work with your cluster, use the facilities of the load balancer to define the offset and length of the string constant. Assuming that the Session ID portion of the session cookie is the default length of 52 bytes, on the load balancer, set: ■ string offset to 53 bytes, the default Random Session ID length plus 1 byte for the delimiter character. ■ string length to 10 bytes If your application or environmental requirements dictate that you change the length of the Random Session ID from its default value of 52 bytes, set the string offset on the load balancer accordingly. The string offset must equal the length of the Session ID plus 1 byte for the delimiter character. Note: It is possible that a cluster member will continue to send multicast heartbeats, but will be unable to process replication requests. This could potentially cause an uneven distribution of secondary servers. When this situation occurs, a warning message is recorded in the server logs. Setting up WebLogic Clusters 10-11

10.2.9 Configure Proxy Plug-Ins