Overview

You can create your own configuration file by specifying a file name with the java.util.logging.config.file system property.

For example:

java -Djava.util.logging.config.file=myfile

When defining a configuration file of your own, the GigaSpaces logging utility is also loaded. Even though both files are loaded, your file does not affect or interrupt the GigaSpaces logging configuration file.

If you do not define any system property, the GigaSpaces logging configuration file is loaded by default.

You can disable the GigaSpaces logging configuration file using the com.gs.logging.disabled system property, though this is not recommended, since you might lose part of the GigaSpaces logging. If com.gs.logging.disabled is set, the system uses the default Java logging settings which are loaded with the JVM:

-Dcom.gs.logging.disabled=true

For GigaSpaces logger loader troubleshooting mode (shows which java logging properties file is loaded and from which location), set:

-Dcom.gs.logging.debug=true

The GigaSpaces logging configuration file can be found under: <GigaSpaces Root>\config\gs_logging.properties.

Global Properties

You can set any of the gs_logging.properties using a system property. For example, if you want to have a separate logger file-handler URL for each process, set:

-Djava.util.logging.FileHandler.pattern=../mypathdir/mylogger.log

The same is true for all other properties, like patterns, log levels, etc.

The classes below must be on the system classpath.

By default, the ConsoleHandler's level is set to ALL, meaning it shows all messages.

Default Global Logging Level

This attribute is ignored by GigaSpaces logging utility.

useParentHandlers is always set to false, to avoid the use of parent logger handlers.

FileHandler Properties

ConsoleHandler Properties

Log Messages Formatting

The com.gigaspaces.logger.GSSimpleFormatter class is used to format messages. This class uses serial numbers, where each number represents a different argument that contains certain data, as seen below:

• 0 – date object.
• 1 – class name if available, logger name otherwise.
• 2 – method name if available, null otherwise.
• 3 – log level.
• 4 – logger name.
• 5 – message.

Default value is:

"{0,date} {0,time}\n{3} [{4}]: {5}\n"

Example of a full-format:

{0,date} {0,time} Class: {1} Method: {2}\n{3} [{4}]: {5}\n

For more details on formatting, see the

class.

When the log component is set to FINER, then GSSimpleFormatter uses a full-format and ignores the supplied (or default) format.

GigaSpaces Loggers

The following properties provide extra control for each logger.

ADMINISTRATIVE

Exception handling:

com.gigaspaces.exceptions.level = SEVERE

When the log message's level is SEVERE, the Exception's stack-trace is logged. At lower levels, only their toString() is logged. To trigger Exception's stack-trace for messages logged with Level.WARNING, set the com.gigaspaces.exceptions.level to WARNING.

MANAGEMENT

GUI, Browser, Cluster View, JMX logging properties:

SERVER

CLIENT

Client side logging properties:

COMMON

Logging properties of common components which vary often used for troubleshooting and produces allot of output:

Service Grid – General

The Service Grid uses a number of different logger components. Each logger component along with what gets logged is listed below:

Service Grid – GSM

GSM logging properties:

Service Grid – GSC

GSC logging properties:

Jini Services

Sets up logging levels for each of the Jini services.

Some of the logging levels are set to OFF. For troubleshooting-related reasons, you can change the logging level to one of the following levels: FINEST, WARNING, CONFIG, etc.

.Net Client

For .Net client logging, see:

• http://www.gigaspaces.com/wiki/display/OLH/.NET+API+Configuration+-+6.0#.NETAPIConfiguration-6.0-LoggingandTracing

Modifying Logger Settings in Runtime using JMX

It us possible to change various logger settings while the system is running without needing to restart it.

This can be very useful in production environments or when the system needs to be troubleshooted, but at the same time cannot be restarted.

This can be achieved using the simple JMX JConsole:

1. In the GigaSpaces Management Center (<GigaSpaces Root\bin\gs-ui.bat/sh), in the Deployments Details tab, right-click the GSC (since the space is running in the GSC), and click Launch JConsole.
2. In JConsole, click the MBeans tab.
3. Expand the java.util.logging tree node and locate the Logging tree node.
4. Select the Operations tab.
5. Type the logger's name and level for the arguments of the setLoggerLevel() method.
   For example, If you want to change the org.jini.rio.monitor.provision level to ALL, type setLoggerLevel(org.jini.rio.monitor.provision, ALL) then click the Refresh button.