The values for the Scheduler Binding Component Loggers start with the location: sun-scheduler-binding. The value text has been wrapped for display purposes.
Specifies the logging level for the entire group of component loggers. Individual logger levels can then be changed as desired.
.com.sun.jbi.common.qos.config.RuntimeConfigurationMBean
.com.sun.jbi.common.qos.discriptor.DeploymentLookup
.com.sun.jbi.common.qos.messaging.MessagingChannel
.com.sun.jbi.common.util.MBeanHelper
.com.sun.jbi.component.toolkit.endpoint.EndpointLifeCycle
.com.sun.jbi.component.toolkit.lifecycle.impl.AcceptPoller
org.glassfish.openesb.schedulerbc.SchedulerComponentManager
org.glassfish.openesb.schedulerbc.SchedulerConfiguration
org.glassfish.openesb.schedulerbc.SchedulerEndpointManager
org.glassfish.openesb.schedulerbc.SchedulerExchangeHandler
org.glassfish.openesb.schedulerbc.SchedulerServiceUnitManager
org.glassfish.openesb.schedulerbc.domain.HybridTrigger
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.