Summary: The status of clustered spaces can be viewed using different logging levels.

Overview

The status of clustered spaces can be viewed using different logging levels. This status is managed by two threads - a Monitor and a Detector.

The Monitor monitors the status of live spaces and reports disconnections, while the Detector detects the status of disconnected spaces and reports reconnection. The space status frequency can be configured using the CONFIG logging level.

See the Proxy Connectivity for details how to tune the Monitor and Detector behavior.

The com.gigaspaces.client.cluster.liveness logger is set by default (in gs_logging.properties) to INFO:

com.gigaspaces.client.cluster.liveness.level = INFO

The different logging levels are detailed below:

Level Description
CONFIG Displays default configurations and available configuration options for both Monitor and Detector threads.
FINE In addition to the CONFIG level, displays disconnections logged by the Monitor and reconnections logged by the Detector.
FINER In addition to the FINE level, displays disconnections logged by user operations and by the detector.
FINEST In addition to the FINEST, displays reconnections logged by user operations and by the detector.

Logging granularity and information assists in tracing the availability of cluster members when using load-balancing or failover policies.

Examples

May 30, 2007 7:13:42 PM
CONFIG [com.gigaspaces.client.cluster.liveness]: [fooSpace] Space status Monitor frequency is configured to 10000 ms.
Use -Dcom.gs.cluster.livenessMonitorFrequency=<value in milliseconds> to configure differently.
May 30, 2007 7:13:42 PM
CONFIG [com.gigaspaces.client.cluster.liveness]: [fooSpace] Space status detector frequency is configured to 5000 ms.
Use -Dcom.gs.cluster.livenessDetectorFrequency=<value in milliseconds> to configure differently.
May 30, 2007 7:14:22 PM
FINE [com.gigaspaces.client.cluster.liveness]: [fooSpace] Space status Monitor disconnected from member: [fooSpace_container1_1:fooSpace]
URL: [jini://*/fooSpace_container1_1/fooSpace?groups=foo-group&ignoreValidation=true]
Caused by: java.rmi.ConnectException: An existing connection was forcefully closed by the remote host; nested exception is:
java.io.IOException: An existing connection was focefully closed by the remote host

May 30, 2007 7:15:27 PM
FINE [com.gigaspaces.client.cluster.liveness]: [fooSpace] Liveness-detector reconnected with Member: [fooSpace_container1_1:foSpace]
URL: [jini://*/fooSpace_container1_1/foSpace?groups=foo-group&ignoreValidation=true]

GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence