Using Dynamic Logger Configuration

The LoggerConfig mechanism (org.jini.rio.log.LoggerConfig; see Javadoc) has been provided for dynamic services (ServiceBeans) can specify named Logger attributes (Levels, Handlers, etc...) in runtime without depending on logger.properties attributes and values to be set.

Using the Logging element in the OperationalString Document

<Logging>
    <Logger Name="examples.hello" Level="ALL">
            <Handler ClassName="java.util.logging.ConsoleHandler" Level="ALL"/>
    </Logger>
</Logging>

If we were to choose a java.util.FileHandler as the Handler the declaration would be as follows:

<Logging>
   <Logger Name="examples.hello" Level="ALL">
       <Handler ClassName="java.util.logging.FileHandler" Level="ALL">
            <Parameters>
               <Parameter Name="java.lang.String" Value="${user.name}/hello%u.log"/>
               <Parameter Name="boolean" Value="true"/>
            </Parameters>
            <Formatter ClassName="java.util.logging.SimpleFormatter"/>
       </Handler>
    </Logger>
</Logging>

Note the use of ${user.name}. This value refers to the value of a system property by using the syntax ${propertyName} within the Value literal. The ${user.name} property gets resolved as the user's account name that is running the JVM the service is instantiated within.

Using LoggerConfig in a Configuration File

import java.util.logging.ConsoleHandler;
import java.util.logging.Level;
import org.jini.rio.log.LoggerConfig;

com.foo {    ...
    loggerConfigs = new LoggerConfig[] {
        new LoggerConfig("com.foo",
                       Level.ALL,
                       false,
                       new LogHandlerConfig[]{
                          new LogHandlerConfig(new ConsoleHandler(), Level.FINE)
                         })
    };
...
}

How the LoggerConfig Gets Created

As part of the ServiceBean instantiation process the LoggerConfig object (if included in the ServiceBean's ServiceBeanConfig object) will be instantiated by GSC infrastructure elements, created the desired Logger configuration (it should be noted that if the Logger already exists, the Level of the Logger being requested using the LogerConfig mechanisms will only be set if the the Level is less then the current Level).

The service can get the named Logger using normal mechanisms (Logger.getLogger("logger-name")).

Loggers

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

RELATED TOPICS

Declaring Elements Globally in Deployment Descriptor

Declaring Service UI in Deployment Descriptor

Deployment Descriptor Codebase Element

Deployment Descriptor DeploymentSchedule Element

Deployment Descriptor Parameters and Configuration Elements

Deployment Descriptor SharedComponent Element

Deployment Descriptor SLA Element

deploy - Service Grid CLI

Fixed and Dynamic ServiceBean ProvisionType

Injecting Deployment Descriptor Properties into POJOs

POJO Lifecycle in Service Grid

Proactive Cache

redeploy - Service Grid CLI

Rio OperationalString

Service Associations

Service Deployment Descriptor

Service Grid ClassLoader Hierarchy

undeploy - Service Grid CLI

Using Service Grid to Deploy Partitioned Space

Using Service Grid to Deploy Partitioned Space with Backup

Using Service Grid to Deploy Replicated Space

Using Service Grid to Deploy Space

Using Service Grid to Deploy Spring Applications

Using System Properties for Deployment Descriptor Element Values