The following table lists each logging code generated by the Scheduler Binding Component and describes the cause of the log message along with the recommended action for you to take.
Logging Code |
Severity |
Message Text, Cause, and Action |
---|---|---|
SCHEDBC-4001 |
Config |
Set Component Configuration {0}: {1} Cause: Component configuration has been changed. Action: None required. |
SCHEDBC-4002 |
Config |
Set Application Configuration {0}: {1} Cause: Application configuration has been changed. Action: None required. |
SCHEDBC-4003 |
Config |
Set Application Variable {0}: {1} Cause: Application variable has been changed. Action: None required. |
SCHEDBC-4004 |
Config |
Using Application Configuration {0} for endpoint {1} Cause: Initialization information. Action: None required. |
SCHEDBC-4005 |
Config |
Scheduler Group via WSDL Configuration: {0} Cause: Initialization information. Action: None required. |
SCHEDBC-4006 |
Config |
Scheduler Date Format via WSDL Configuration: {0} Cause: Initialization information. Action: None required. |
SCHEDBC-4007 |
Config |
Scheduler Mode via WSDL Configuration: {0} Cause: Initialization information. Action: None required. |
SCHEDBC-4008 |
Config |
Scheduler Start date via WSDL Configuration: {0} Cause: Initialization information. Action: None required. |
SCHEDBC-4009 |
Config |
Scheduler End date via WSDL Configuration: {0} Cause: Initialization information. Action: None required. |
SCHEDBC-4010 |
Config |
Scheduler Time Zone via WSDL Configuration: {0} Cause: Initialization information. Action: None required. |
SCHEDBC-4011 |
Config |
Scheduler Start date overridden by Application Configuration: {0} Cause: The WSDL configuration was overridden by the application during initialization. Action: None required. |
SCHEDBC-4012 |
Config |
Scheduler End date overridden by Application Configuration: {0} Cause: The WSDL configuration was overridden by the application during initialization. Action: None required. |
SCHEDBC-4013 |
Config |
Scheduler Time Zone overridden by Application Configuration: {0} Cause: The WSDL configuration was overridden by the application during initialization. Action: None required. |
SCHEDBC-4014 |
Config |
Scheduler trigger {0}.{1} not enabled and thus bypassed Cause: Initialization information. Action: Enable trigger in WSDL if not intentional. |
SCHEDBC-4015 |
Config |
Quartz Scheduler job name {0} will be scheduled Cause: Initialization information. Action: None required. |
SCHEDBC-4016 |
Config |
Quartz Scheduler job descripton: {0} Cause: Initialization information. Action: None required. |
SCHEDBC-4017 |
Config |
Scheduling {0} trigger {1}.{2} to fire {3} times, every {4} milliseconds Cause: Initialization information. Action: None required. |
SCHEDBC-4018 |
Config |
Scheduling {0} trigger {1}.{2} to fire for condition: {3} Cause: Initialization information. Action: None required. |
SCHEDBC-4019 |
Config |
Obfuscated Password Application Variable {0} Cause: Initialization information. Action: None required. |
SCHEDBC-4020 |
Config |
Created Quartz Scheduler {0} with {1} worker threads Cause: Initialization information. Action: None required. |
SCHEDBC-4021 |
Config |
Scheduling {0} trigger {1}.{2} to fire for condition: {3} to last {4} millisecs, repeating {5} times at {6} millisecs interval Cause: Initialization information. Action: None required. |
SCHEDBC-5001 |
Info |
Start Scheduler consumer endpoints... Cause: Information details. Action: None required. |
SCHEDBC-5002 |
Info |
Stopped Scheduler consumer endpoints Cause: Information details. Action: None required. |
SCHEDBC-5003 |
Info |
Shut down Scheduler consumer endpoints... Cause: Information details. Action: None required. |
SCHEDBC-5004 |
Info |
Creating endpoint for {0} Cause: Information details. Action: None required. |
SCHEDBC-5005 |
Info |
Quartz Scheduler has been started Cause: Information details. Action: None required. |
SCHEDBC-5006 |
Info |
Quartz Scheduler has been shut down Cause: Information details. Action: None required. |
SCHEDBC-5007 |
Info |
Quartz Scheduler has been suspended Cause: Information details. Action: None required. |
SCHEDBC-5008 |
Info |
{0} trigger {1}.{2} will fire first at: {3} Cause: Information details. Action: None required. |
SCHEDBC-6001 |
Warning |
SchedulerBootstrap installation MBean failed to initialize: {0} Cause: [Rare] A deleted or corrupted component descriptor file (for example, JavaCAPSHome\glassfish\domains\domain1\jbi\components\sun-scheduler-binding\install_root\META-INF\jbi.xml) . Action: Reinstall the Scheduler BC. |
SCHEDBC-6003 |
Warning |
Cannot shutdown Quartz Scheduler Cause: OpenSymphony Quartz Scheduler cannot be shut down. Action: Try shutting down and then restarting the application server. |
SCHEDBC-6004 |
Warning |
Cannot start Quartz Scheduler Cause: OpenSymphony Quartz Scheduler cannot be started or resumed. Action: Try shutting down and then restarting the application server. |
SCHEDBC-6005 |
Warning |
Cannot suspend Quartz Scheduler Cause: OpenSymphony Quartz Scheduler cannot be suspended. Action: Try shutting down and then restarting the application server. |
SCHEDBC-6006 |
Warning |
Consumer endpoint {0} cannot send to (consume) provider endpoint Cause: Provider endpoint is failing to respond. Action: Try stopping and restarting the provider endpoint component or resuming it if it has been suspended by its QoS configuration. |
SCHEDBC-6007 |
Warning |
Cannot find Scheduler consumer endpoint {0} from Component context Cause: [Rare] The JBI framework is malfunctioning. Action: Try shutting down and then restarting the application server. |
SCHEDBC-6008 |
Warning |
Application variable {0} is undefined Cause: The application variable noted in the error message is referenced in the trigger message but it has not been defined. Action: Define the application variable and then redeploy the respective Composite Application project . |
SCHEDBC-6009 |
Warning |
Invalid timezone ID ({0}) specified; using default instead Cause: An invalid timezone ID was manually specified. Action: Use the WSDL editor to select one of the valid IDs from the drop-down list. |
SCHEDBC-6010 |
Warning |
Got SchedulerException in {0}: Cause: [Rare] Cannot find the Quartz API Version from the quartz-all.jar file. Action: Try reinstalling the Scheduler BC. |
SCHEDBC-6011 |
Warning |
Interrupted, so abort waiting for Message Exchange ACK/NACK Cause: The Java VM was interrupted while waiting on the disposition of a Message Exchange. Action: None required. The GlassFish application server is probably shutting down. |
SCHEDBC-6012 |
Warning |
Failed {0} attempt(s) to consume provider endpoint, disposing this trigger message instance "{1}" Cause: The QoS is configured to delete this triggering message when the number of allowed attempts to retry have been exhausted. Action: Verify that the provider endpoint is functioning properly or readjust the QoS configuration as needed. |
SCHEDBC-6013 |
Warning |
Failed {0} attempt(s) to consume provider endpoint, flagging this trigger message instance "{1}" as FAILED in Quartz Cause: The QoS is configured to error out this triggering message when the number of allowed attempts to retry have been exhausted. Action: Verify that the provider endpoint is functioning properly or readjust the QoS configuration as needed. |
SCHEDBC-6014 |
Warning |
Failed {0} attempt(s) to consume provider endpoint with this trigger message "{1}"; SUSPEND is NOT however supported by this component Cause: The QoS is configured to suspend this endpoint when the number of allowed attempts to resend the trigger message have been exhausted. Action: Suspend is not supported, so the Scheduler BC consumer endpoint remains active. Verify that the provider endpoint is functioning properly or readjust the QoS configuration as needed. |
SCHEDBC-6015 |
Warning |
Failed to consume provider endpoint with this trigger message "{0}" Cause: QoS redelivery has not been configured for this Scheduler BC endpoint and it cannot send the message to the provider . Action: Verify that the provider endpoint is functioning properly or readjust the QoS configuration as needed. |
SCHEDBC-6016 |
Warning |
Failed {0} attempt(s) to consume intended provider with this trigger message "{1}"; redirected to {2}-{3} Cause: The QoS is configured to redirect this trigger message to another provider endpoint when the number of allowed attempts to resend it have been exhausted. Action: Verify that the provider endpoint is functioning properly or readjust the QoS configuration as needed. |
SCHEDBC-6017 |
Warning |
Interrupted, so abort waiting in throttling queue Cause: The Java VM was interrupted while waiting to send a trigger message. Action: None required. The GlassFish application server is probably shutting down. |
SCHEDBC-7001 |
Severe |
Cannot create Quartz Scheduler for Service Assembly {0} Cause: Problems were encountered while creating an OpenSymphony Quartz Scheduler. Action: Try shutting down and restarting the Scheduler BC or the GlassFish application server. |
SCHEDBC-7002 |
Severe |
Cannot find respective Scheduler endpoint Cause: [Rare] The JBI framework is likely malfunctioning. Action: Try shutting down and restarting the GlassFish application server. |
SCHEDBC-7003 |
Severe |
WSDL for Endpoint {0} does not represent a valid Scheduler binding Cause: No appropriate Scheduler BC binding WSDL was found in the service unit. Action: Ensure that the respective project involving the Scheduler BC has an appropriate binding WSDL specified and redeploy the Composite Application. |
SCHEDBC-7004 |
Severe |
Cannot initialize Scheduler for endpoint {0} Cause: Cannot initialize the Scheduler for non-specific reasons. Action: Verify that the Scheduler BC binding WSDL is correct and redeploy the Composite Application. |