Oracle Coherence Monitor

User Guide

 

Using the Monitor - OC Administration
These displays allow you to manage your Oracle Coherence metrics, nodes and caches. Some of these displays might be read-only depending on your login.

NOTE: Click the button to view the current display in a new window.

OC Metrics Administration
 This display allows various statistics to be reset, so that cumulative data can be visualized more meaningfully. It is read-only unless you are logged in as admin or super.

Cluster Select a cluster from the drop-down menu.
   
Connection The name of the JMX connection used to access the cluster data.
 
Reset Service Statistics Click to reset the cumulative counts of the service statistics.
Reset Cache Statistics Click to reset the cumulative counts of the cache statistics.
Reset Node Statistics Click to reset the cumulative counts of the node statistics.
Reset Connection Statistics Click to reset the cumulative counts of the connection statistics.
 
Total MBeans Queried Node MBeans Total number of node MBeans queried.
Service MBeans Total number of service MBeans queried.
Cache MBeans Total number of cache MBeans queried.
Storage MBeans Total number of storage MBeans queried.
JVM Platform MBeans Total number of JVM platform MBeans queried.
Total Total number of MBeans queried.
 
RTView Memory Utilization for Metrics History By default, the Oracle Coherence Monitor stores several hours of data using in-memory tables.
Cache Metrics, # Rows  The number of table rows used by the OC Monitor to store cache metrics data.
Cache Metrics, Memory Used (KB) The amount of memory (KB) used by the OC Monitor to store cache metrics data.
Node Metrics, # Rows The number of table rows used by the OC Monitor to store node metrics data.
Node Metrics, Memory Used (KB) The amount of memory (KB) used by the OC Monitor to store node metrics data.
 
Total RTView JMX Query Time Total amount of time, in milliseconds, to query the monitoring MBeans from Coherence.
Time Range Select a time range or All Data from the drop-down menu. By default, the ending period for displayed data is the current time. To specify a time range:

1. Click the  button to open the calendar dialog. By default, the time range end point is the current time.

2. Change the time range end point by clicking the  button and selecting the date and time, then click OK. Or enter the date and time in the text field using the following format: MMM dd, YYYY HH:MM:ss. For example, Apr 26, 2012 5:01 PM.

3. Click Apply. The navigation arrows  appear. 

4. Use the navigation arrows  to move forward or backward one time period (the time period selected from the Time Range drop-down menu). Click Restore to Now to reset the time range end point to the current time.

 

Management Settings
 This display is read-only unless you are logged in as admin or super.

Cluster Select a cluster from the drop-down menu.
 
JMX Connection The name of the JMX connection used to access the cluster data.
 
JMX Management Settings Refresh Policy Select a refresh policy from the drop-down list.
refresh-expired Each MBean will be refreshed from the remote node when it is accessed and the expiry delay has passed from the last refresh (same functionality as in pre-3.4 Coherence releases.

This option is the default setting and is best used when MBeans are accessed in a random pattern.

refresh-ahead MBeans are refreshed before they are requested based on prior usage patterns after the expiry delay has passed, reducing latency of management information with a minor increase in network consumption.

This option is best when MBeans are accessed in a repetitive/programmatic pattern.

refresh-behind Each MBean will be refreshed after the data is accessed, ensuring optimal response time. However, note that the information returned will be offset by the last refresh time.
refresh-onquery Select this option if the refresh-on-query MBeanServer is configured.
Expiry Delay Duration (in milliseconds) that the MBeanServer will keep a remote model snapshot before refreshing.
Refresh on Query Specifies whether or not the refresh-on-query MBeanServer is configured. If so, then set the RefreshPolicy to refresh-onquery.
 
Refresh Time The timestamp when this model was last retrieved from a corresponding node. For local servers it is the local time.
Refresh Count* The total number of snapshots retrieved since the statistics were last reset.
Refresh Excess Count* The number of times the MBean server predictively refreshed information and the information was not accessed.
Refresh Timeout Count* The number of times this management node has timed out while attempting to refresh remote MBean attributes.
Refresh Prediction Count* The number of times the MBeanServer used a predictive (refresh-behind, refresh-ahead, refresh-onquery) algorithm to refresh MBean information.

*Delta values show the change in the counts within the most recent JMX retrieval period.

Node Administration
 This display allows the user to view and change settings for individual Nodes. It is read-only unless you are logged in as super. Click on the desired Node to select that Node. Change the data item in the bottom half of the display and press Return to make the change. All data on this display is queried from and set on the Coherence ClusterNodeMBean.

Cluster Select a cluster from the drop-down menu.
   
Current Settings for All Nodes Location A unique identifier for each node. It is defined as: member_name.machine.rack.site.
BufferPublishSize The buffer size of the unicast datagram socket used by the Publisher, measured in the number of packets. Changing this value at runtime is an inherently unsafe operation that will pause all network communications and may result in the termination of all cluster services.
BufferReceiveSize The buffer size of the unicast datagram socket used by the Receiver, measured in the number of packets. Changing this value at runtime is an inherently unsafe operation that will pause all network communications and may result in the termination of all cluster services.
BurstCount The maximum number of packets to send without pausing. Anything less than one (e.g. zero) means no limit.
BurstDelay The number of milliseconds to pause between bursts. Anything less than one (e.g. zero) is treated as one millisecond.
MulticastThreshold The percentage (0 to 100) of the servers in the cluster that a packet will be sent to, above which the packet will be multicasted and below which it will be unicasted.
ResendDelay The minimum number of milliseconds that a packet will remain queued in the Publisher`s re-send queue before it is resent to the recipient(s) if the packet has not been acknowledged. Setting this value too low can overflow the network with unnecessary repetitions. Setting the value too high can increase the overall latency by delaying the re-sends of dropped packets. Additionally, change of this value may need to be accompanied by a change in SendAckDelay value.
SendAckDelay The minimum number of milliseconds between the queueing of an Ack packet and the sending of the same. This value should be not more then a half of the ResendDelay value
TrafficJamCount The maximum total number of packets in the send and resend queues that forces the publisher to pause client threads. Zero means no limit.
TrafficJamDelay The number of milliseconds to pause client threads when a traffic jam condition has been reached. Anything less than one (e.g. zero) is treated as one millisecond.
LoggingLevel Specifies which logged messages will be output to the log destination. Valid values are non-negative integers or -1 to disable all logger output.
LoggingLimit The maximum number of characters that the logger daemon will process from the message queue before discarding all remaining messages in the queue. Valid values are integers in the range [0...]. Zero implies no limit.
LoggingFormat Specifies how messages will be formatted before being passed to the log destination
LoggingDestination The output device used by the logging system. Valid values are stdout, stderr, jdk, log4j, or a file name.
nodeld The short Member id that uniquely identifies the Member at this point in time and does not change for the life of this Member.
ProcessName A configured name that should be the same for Members that are in the same process (JVM), and different for Members that are in different processes. If not explicitly provided, for processes running with JRE 1.5 or higher the name will be calculated internally as the Name attribute of the system RuntimeMXBean, which normally represents the process identifier (PID).
 
Selected Node(s) Lists the nodes selected in the table.
Select All Nodes Click to select all nodes.
 
Shutdown Node Stop all the clustered services running at this node (controlled shutdown). The management of this node will node be available until the node is restarted (manually or programmatically).
Ensure Cache Service Ensure that a CacheService for the specified cache runs at the cluster node represented by this MBean. This method will use the configurable cache factory to find out which cache service to start if necessary. Return value indicates the service name; null if a match could not be found.
Ensure Invocation Ensure that an InvocationService with the specified name runs at the cluster node represented by this MBean.

 

Cache Administration 
 This display allows the user to view and change settings for individual caches. It is read-only unless you are logged in as super. Click on the desired cache to select that cache. Change the data item in the bottom half of the display and press Return to make the change. The data on this display is queried from and set on the Coherence CacheMBean.

Cluster Select a cluster from the drop-down menu.
 
Service Select the service to display.
Cache Select the cache to display.
Front Select for front tier, deselect for back tier.
 
Current Settings for all Nodes on Selected Cache Location A unique identifier for each node. It is defined as:  member_name.machine.rack.site.
LowUnits The number of units to which the cache will shrink when it prunes. This is often referred to as a `low water mark` of the cache.
HighUnits The limit of the cache size measured in units. The cache will prune itself automatically once it reaches its maximum unit level. This is often referred to as the `high water mark` of the cache.
BatchFactor The BatchFactor attribute is used to calculate the `soft-ripe` time for write-behind queue entries. A queue entry is considered to be `ripe` for a write operation if it has been in the write-behind queue for no less than the QueueDelay interval. The `soft-ripe` time is the point in time prior to the actual `ripe` time after which an entry will be included in a batched asynchronous write operation to the CacheStore (along with all other `ripe` and `soft-ripe` entries). This attribute is only applicable if asynchronous writes are enabled (i.e. the value of the QueueDelay attribute is greater than zero) and the CacheStore implements the storeAll() method. The value of the element is expressed as a percentage of the QueueDelay interval. Valid values are doubles in the interval [0.0, 1.0].
ExpiryFactor The time-to-live for cache entries in milliseconds. Value of zero indicates that the automatic expiry is disabled. Change of this attribute will not affect already-scheduled expiry of existing entries.
FlushDelay The number of milliseconds between cache flushes. Value of zero indicates that the cache will never flush.
QueueDelay The number of seconds that an entry added to a write-behind queue will sit in the queue before being stored via a CacheStore. Applicable only for WRITE-BEHIND persistence type.
RefreshFactor The RefreshFactor attribute is used to calculate the `soft-expiration` time for cache entries. Soft-expiration is the point in time prior to the actual expiration after which any access request for an entry will schedule an asynchronous load request for the entry. This attribute is only applicable for a ReadWriteBackingMap which has an internal LocalCache with scheduled automatic expiration. The value of this element is expressed as a percentage of the internal LocalCache expiration interval. Valid values are doubles in the interval[0.0, 1.0]. If zero, refresh-ahead scheduling will be disabled.
Requeue Threshold The maximum size of the write-behind queue for which failed CacheStore write operations are requeued. If zero, the write-behind requeueing will be disabled. Applicable only for WRITE-BEHIND persistence type.
nodeld The node ID.
 
Selected Node(s) Lists the nodes selected in the table.
Select All Nodes Click to select all nodes in the table.

 

 

 


 

RTView contains components licensed under the Apache License Version 2.0.

 

Treemap Algorithms v1.0  is used without modifications and licensed by MPL Version 1.1. Copyright © 2001 University of Maryland, College Park, MD

 

Datejs is licensed under MIT. Copyright © Coolite Inc.

 

jQuery is licensed under MIT. Copyright © John Resig,

 

JCalendar 1.3.2 is licensed under LGPL. Copyright © Kai Toedter.

 

jQuery is licensed under MIT. Copyright (c) 2009 John Resig, http://jquery.com/ JCalendar 1.3.2 is licensed under LGPL. Copyright © Kai Toedter.

 

JMS, JMX and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. They are mentioned in this document for identification purposes only. 

 

SL, SL-GMS, GMS, RTView, SL Corporation, and the SL logo are trademarks or registered trademarks of Sherrill-Lubinski Corporation in the United States and other countries. Copyright © 1998-2013 Sherrill-Lubinski Corporation. All Rights Reserved.