| |
Clusters: Monitoring
Configuration Options Related Tasks Related Topics
This page allows you to monitor the status of servers that are in this cluster. All members of the cluster are displayed in the table regardless of their current state.
Configuration Options
Name Description Name Machine The WebLogic Server host computer (machine) on which this server is meant to run.
If you want to use Node Manager to start this server, you must assign the server to a machine and you must configure the machine for Node Manager.
You cannot change this value if a server instance is already running.
MBean Attribute:
ServerMBean.MachineChanges take effect after you redeploy the module or restart the server.
Listen Address The IP address or DNS name this server uses to listen for incoming connections.
Servers can be reached through the following URL:
protocol://listen-address:listen-portAny network channel that you configure for this server can override this listen address.
If a server's listen address is undefined, clients can reach the server through an IP address of the computer that hosts the server, a DNS name that resolves to the host, or the localhost string. The localhost string can be used only for requests from clients that are running on the same computer as the server.
If you want to limit the valid addresses for a server instance, specify one of the following:
IP address. If you provide an IP address, clients can specify either the IP address or a DNS name that maps to the IP address. Clients that specify an IP address and attempt to connect through an SSL port must disable hostname verification.
DNS name. If you provide a DNS name, clients can specify either the DNS name or the corresponding IP address.
Do not leave the listen address undefined on a computer that uses multiple IP address (a multihomed computer). On such a computer, the server will bind to all available IP addresses.
- Notes:
To resolve a DNS name to an IP address, WebLogic Server must be able to contact an appropriate DNS server or obtain the IP address mapping locally. Therefore, if you specify a DNS name for the listen address, you must either leave a port open long enough for the WebLogic Server instance to connect to a DNS server and cache its mapping or you must specify the IP address mapping in a local file. If you specify an IP address for ListenAddress and then a client request specifies a DNS name, WebLogic Server will attempt to resolve the DNS name, but if it cannot access DNS name mapping, the request fails.
Note also that if you are using the demo certificates in a multi-server domain, Managed Server instances will fail to boot if you specify the fully-qualified DNS name. For information about this limitation and suggested workarounds, see "Limitation on CertGen Usage" in Administering Security for Oracle WebLogic Server.
MBean Attribute:
ServerMBean.ListenAddressChanges take effect after you redeploy the module or restart the server.
Listen Port The default TCP port that this server uses to listen for regular (non-SSL) incoming connections.
Administrators must have the right privileges before binding to a port or else this operation will not be successful and it will render the console un-reachable.
If this port is disabled, the SSL port must be enabled. Additional ports can be configured using network channels. The cluster (multicast) port is configured separately.
MBean Attribute:
ServerMBean.ListenPortMinimum value:
1Maximum value:
65535State Master Indicates whether the server is the ClusterMaster of a cluster which is configured for server migration.
Health Expected To Run JVM ID Heap Size Current Heap Free Current Open Sockets Current Count Sockets Opened Total Count Weblogic Version OS Version Resend Requests Provides the number of state-delta messages that had to be resent because a receiving server in the cluster missed a message.
Returns the number of state-delta messages that had to be resent because a receiving server in the cluster missed a message.
MBean Attribute:
ClusterRuntimeMBean.ResendRequestsCountFragments Sent Returns the total number of message fragments sent from this server into the cluster. This is applicable to both multicast and unicast message types.
MBean Attribute:
ClusterRuntimeMBean.FragmentsSentCountFragments Received Provides the total number of messages received on this server from the cluster. This is applicable to both multicast and unicast message types.
MBean Attribute:
ClusterRuntimeMBean.FragmentsReceivedCountMessages Lost Provides the total number of in-coming multicast messages that were lost according to this server.
MBean Attribute:
ClusterRuntimeMBean.MulticastMessagesLostCountForeign Fragments Dropped Provides the number of fragments that originated in foreign domains or clusters which use the same multicast address.
Answer the number of fragments that originated in foreign domains/cluster that use the same multicast address.
MBean Attribute:
ClusterRuntimeMBean.ForeignFragmentsDroppedCountRemote Groups Discovered Returns the total groups discovered by this server
MBean Attribute:
UnicastMessagingRuntimeMBean.RemoteGroupsDiscoveredCountLocal Group Leader Name of the local group leader
MBean Attribute:
UnicastMessagingRuntimeMBean.LocalGroupLeaderNameTotal Groups Total configured groups - running and not running
MBean Attribute:
UnicastMessagingRuntimeMBean.TotalGroupsCountDiscovered Group Leaders Running group leader names
MBean Attribute:
UnicastMessagingRuntimeMBean.DiscoveredGroupLeadersGroups Formatted group list
MBean Attribute:
UnicastMessagingRuntimeMBean.GroupsPrimary Provides the number of object that the local server hosts as primaries.
Answer the number of object that the local server hosts as primaries.
MBean Attribute:
ClusterRuntimeMBean.PrimaryCountSecondary Distribution Names Provides the names of the remote servers (such as myserver) for which the local server is hosting secondary objects. The name is appended with a number to indicate the number of secondaries hosted on behalf of that server.
MBean Attribute:
ClusterRuntimeMBean.SecondaryDistributionNamesDrop-out Frequency A relative measure of the number of times that a server has become unreachable from the cluster perspective.
|