Dynamic Cluster Address If you do not explicitly define a cluster address
10.1.5.6.1 Dynamic Cluster Address If you do not explicitly define a cluster address
when you configure a cluster, when a clustered server instance receives a remote request, WebLogic Server generates the cluster address, in the form: listenaddress1:listenport1,listenaddress2:listenport2;listenaddress3: listenport3 Each listen address:listen port combination in the cluster address corresponds to Managed Server and network channel that received the request. ■ If the request was received on the Managed Servers default channel, the listen address:listen port combinations in the cluster address reflect the ListenAddress and ListenPort values from the associated ServerMBean and SSLMBean instances. For more information, see The Default Network Channel in Configuring Server Environments for Oracle WebLogic Server. ■ If the request was received on a custom network channel, the listen address:listen port in the cluster address reflect the ListenAddress and ListenPort values from NetworkAccessPointMBean that defines the channel. For more information about network channels in a cluster, see Configuring Network Channels For a Cluster in Configuring Server Environments for Oracle WebLogic Server. The number of ListenAddress:ListenPort combinations included in the cluster address is governed by the value of the NumberOfServersInClusterAddress attribute on the ClusterMBean, which is 3 by default. You can modify the value of NumberOfServersInClusterAddress on the Environments Clusters ClusterName Configuration General page of the Administration Console. ■ If there are fewer Managed Servers available in the cluster than the value of NumberOfServersInClusterAddress, the dynamically generated cluster address contains a ListenAddress:ListenPort combination for each of the running Managed Servers. ■ If there are more Managed Servers available in the cluster than the value of NumberOfServersInClusterAddress, WebLogic Server randomly selects a subset of the available instances—equal to the value of NumberOfServersInClusterAddress—and uses the ListenAddress:ListenPort combination for those instances to form the cluster address. The order in which the ListenAddress:ListenPort combinations appear in the cluster address is random—from request to request, the order will vary.10.1.5.6.2 Explicitly Defining Cluster Address for Production Environments If you explicitly
Parts
» Oracle Fusion Middleware Online Documentation Library
» Document Scope and Audience Guide to this Document
» What Are the Benefits of Clustering? What Are the Key Capabilities of a Cluster?
» Servlets and JSPs EJBs and RMI Objects
» Getting Connections with Clustered JDBC Failover and Load Balancing for JDBC Connections
» Pure-Java Versus Native Socket Reader Implementations
» Client Communication via Sockets
» How WebLogic Server Creates the Cluster-Wide JNDI Tree
» How WebLogic Server Updates the JNDI Tree Client Interaction with the Cluster-Wide JNDI Tree
» Load Balancer Configuration Requirements Load Balancers and the WebLogic Session Cookie
» Related Programming Considerations How Session Connection and Failover Works with a Load Balancer
» Round-Robin Load Balancing Weight-Based Load Balancing
» Transactional Collocation Optimization for Collocated Objects
» Methods of Configuring Clusters Load Balancing for JDBC Connections
» Using Replication Groups HTTP Session State Replication
» Connection with Load Balancing Hardware Failover with Load Balancing Hardware
» Configuration Requirements for Cross-Cluster Replication
» Configuring Session State Replication Across Clusters
» Clustering Objects with Replica-Aware Stubs
» Failover and JDBC Connections Understanding Server and Service Migration
» Migration Terminology Oracle Fusion Middleware Online Documentation Library
» Features That Use Leasing Leasing Versions
» Determining Which Type of Leasing To Use High-availability Database Leasing
» Non-database Consensus Leasing Leasing
» Preparing for Automatic Whole Server Migration
» Configuring Automatic Whole Server Migration
» Startup Process in a Cluster with Migratable Servers
» Automatic Whole Server Migration Process
» Manual Whole Server Migration Process Administration Server Role in Whole Server Migration
» Migratable Server Behavior in a Cluster Node Manager Role in Whole Server Migration
» Cluster Master Role in Whole Server Migration
» JMS-related Services JTA Transaction Recovery Service
» Custom Store Availability for JMS Services Default File Store Availability for JTA
» Best Practices for Targeting JMS when Configuring Automatic Service Migration
» Architecture Web Application Tiers
» Combined Tier Architecture De-Militarized Zone DMZ Load Balancer Proxy Plug-In
» No Collocation Optimization Firewall Restrictions
» Multi-Tier Proxy Architecture Proxy Architecture Benefits Proxy Architecture Limitations
» Proxy Plug-In Versus Load Balancer
» DMZ with Two Firewall Configuration
» Dynamic Cluster Address If you do not explicitly define a cluster address
» Configuration Roadmap Install WebLogic Server
» Starting a WebLogic Server Cluster
» Configure Node Manager Configure Load Balancing Method for EJBs and RMIs
» Sample web.xml This section contains a sample deployment descriptor file
» Accessing Applications Via the Proxy Server Ensure that applications clients will
» Configure Replication Groups Configure Migratable Targets for Pinned Services
» Migrating When the Currently Active Host is Unavailable Use this migration
» Configure Multicast Time-To-Live TTL Configure Multicast Buffer Size
» Cluster-Related Configuration Options Follow Usage and Configuration Guidelines
» Manual Migration of the JTA Transaction Recovery Service State Management in a Cluster
» Naming Considerations Administration Server Considerations
» Firewall Considerations Avoiding Problems
» Check the Server Version Numbers Check the Multicast Address Check the CLASSPATH Value
Show more