Logger Properties

The Scheduler Binding Component runtime Logger properties include 13 different component activities that can be monitored and recorded at user-designated levels.

Each logger can be set to record information at any of the following levels:

• FINEST: messages provide highly detailed tracing

• FINER: messages provide reasonably detailed tracing

• FINE: messages provide basic tracing

• CONFIG: provides static configuration messages

• INFO: provides informative messages

• WARNING: messages indicate a warning

• SEVERE: messages indicate a severe failure

• OFF: no logging messages

Scheduler Binding Component Loggers

The values for the Scheduler Binding Component Loggers start with the location: sun-scheduler-binding. The value text has been wrapped for display purposes.

sun-scheduler-binding

Specifies the logging level for the entire group of component loggers. Individual logger levels can then be changed as desired.

RuntimeConfigurationMBean

.com.sun.jbi.common.qos.config.RuntimeConfigurationMBean

Deployment Lookup (QoS)

.com.sun.jbi.common.qos.discriptor.DeploymentLookup

Messaging Channel (QoS)

.com.sun.jbi.common.qos.messaging.MessagingChannel

MBeanHelper

.com.sun.jbi.common.util.MBeanHelper

EndpointLifeCycle

.com.sun.jbi.component.toolkit.endpoint.EndpointLifeCycle

Accept Poller Thread (Comp TK)

.com.sun.jbi.component.toolkit.lifecycle.impl.AcceptPoller

SchedulerBC Component Manager

org.glassfish.openesb.schedulerbc.SchedulerComponentManager

SchedulerBC Configuration Manager

org.glassfish.openesb.schedulerbc.SchedulerConfiguration

SchedulerBC Endpoint Manager

org.glassfish.openesb.schedulerbc.SchedulerEndpointManager

SchedulerBC Exchange Handler

org.glassfish.openesb.schedulerbc.SchedulerExchangeHandler

SchedulerBC Service Unit Manager

org.glassfish.openesb.schedulerbc.SchedulerServiceUnitManager

SchedulerBC Hybrid Trigger

org.glassfish.openesb.schedulerbc.domain.HybridTrigger

SchedulerBC Endpoint Handler

org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint

Exception messages start with a unique identifier. The Scheduler Binding Component exception message starts with SCHEDBC. For example:

SCHEDBC-3005: Quartz Cron trigger cronBinding.CronTrigger1 will fire next at:
2008-12-08T12:45:00.000-0800
COMPTK-3001: Message exchange accepted from NMR: 
id=40556676730368-18686-134480792400230253,role=CONSUMER,status=Done
COMPTK-3009: Stopping SU-QosDemoCA-sun-scheduler-binding

For more information about the Scheduler Binding Component Logging Codes, see Logging Codes By Component.