The following table lists each alert code generated by the Scheduler Binding Component and describes the cause of the alert along with the recommended action for you to take.
Alert Code |
Severity |
Alert Text, Cause, and Action |
---|---|---|
SCHEDBC-5001 |
Info |
Start Scheduler consumer endpoints. Cause: Informational message. Action: None required. |
SCHEDBC-5002 |
Info |
Stopped Scheduler consumer endpoints. Cause: Informational detail. Action: None required. |
SCHEDBC-5003 |
Info |
Shut down Scheduler consumer endpoints. Cause: Informational detail. Action: None required. |
SCHEDBC-5004 |
Info |
Creating endpoint for {0}. Cause: Informational detail. Action: None required. |
SCHEDBC-5005 |
Info |
Quartz Scheduler has been started. Cause: Informational detail. Action: None required. |
SCHEDBC-5006 |
Info |
Quartz Scheduler has been shut down. Cause: Informational detail. Action: None required. |
SCHEDBC-5007 |
Info |
Quartz Scheduler has been suspended. Cause: Informational detail. Action: None required. |
SCHEDBC-5008 |
Info |
{0} trigger {1}.{2} will fire first at: {3}. Cause: Informational detail. Action: None required. |
SCHEDBC-6001 |
Warning |
SchedulerBootstrap installation MBean failed to initialize: {0}. Cause: [Rare] A deleted or corrupted Component Descriptor file (for example, C:\JavaCAPS6U2\glassfish\domains\domain1\jbi\components\sun-scheduler-binding\install_root\META-INF\jbi.xml). Action: Reinstall the Scheduler Binding Component. |
SCHEDBC-6003 |
Warning |
Cannot shutdown Quartz Scheduler. Cause: OpenSymphony Quartz Scheduler cannot be shut down. Action: Try cycling (shut down then restart) GlassFish Application Server. |
SCHEDBC-6004 |
Warning |
Cannot start Quartz Scheduler. Cause: OpenSymphony Quartz Scheduler cannot be started or resumed. Action: Try cycling GlassFish Application Server. |
SCHEDBC-6005 |
Warning |
Cannot suspend Quartz Scheduler. Cause: OpenSymphony Quartz Scheduler cannot be suspended. Action: Try cycling GlassFish Application Server. |
SCHEDBC-6006 |
Warning |
Consumer endpoint {0} cannot send to (consume) provider endpoint. Cause: Provider endpoint is down or unresponsive. Action: Try cycling the provider endpoint component, or try 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] JBI framework malfunctioning. Action: Try cycling GlassFish Application Server. |
SCHEDBC-6008 |
Warning |
Application variable {0} is undefined. Cause: The above mentioned Application variable is referenced in the trigger message but has not been defined. Action: Define it and redeploy the respective Composite Application project. |
SCHEDBC-6009 |
Warning |
Invalid timezone ID ({0}) specified; using default instead. Cause: An invalid timezone ID was specified manually. 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. Action: Try reinstalling Scheduler Binding Component. |
SCHEDBC-6011 |
Warning |
Interrupted, so abort waiting for Message Exchange ACK/NACK. Cause: Java VM was interrupted while waiting on the disposition of a Message Exchange. Action: None, GlassFish Application Server is probably being aborted. |
SCHEDBC-6012 |
Warning |
Failed {0} attempt(s) to consume provider endpoint, disposing this trigger message instance "{1}". Cause: QoS configured to Delete this triggering message when specified attempts to retry have been exhausted. Action: Verify that the provider endpoint is functioning properly, or re-adjust the QoS configuration appropriately. |
SCHEDBC-6013 |
Warning |
Failed {0} attempt(s) to consume provider endpoint, flagging this trigger message instance "{1}" as FAILED in Quartz. Cause: The QoS property is configured to error out this triggering message when specified attempts to retry have been exhausted. Action: Verify that the provider endpoint is functioning properly, or re-adjust the QoS configuration appropriately. |
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 property is configured to Suspend this endpoint when specified attempts to resend the trigger message have been exhausted. Action: Suspend is not supported so the Scheduler Binding Component consumer endpoint remains active. Verify that the provider endpoint is functioning properly, or re-adjust the QoS configuration as appropriate. |
SCHEDBC-6015 |
Warning |
Failed to consume provider endpoint with this trigger message "{0}". Cause: QoS Redelivery has not been configured for this Scheduler Binding Component endpoint and it cannot send the message on to the provider. Action: Verify that the provider endpoint is functioning properly, or re-adjust the QoS configuration as appropriate. |
SCHEDBC-6016 |
Warning |
Failed {0} attempt(s) to consume intended provider with this trigger message "{1}"; redirected to {2}-{3}. Cause: The QoS property is configured to Redirect this trigger message to another provider endpoint when specified attempts to resend it have been exhausted. Action: Verify that the provider endpoint is functioning properly, or re-adjust the QoS configuration as appropriate. |
SCHEDBC-6017 |
Warning |
Interrupted, so abort waiting in throttling queue. Cause: Java VM has been interrupted while waiting to send a trigger message. Action: None, GlassFish Application Server is probably being aborted. |
SCHEDBC-7001 |
Critical |
Cannot create Quartz Scheduler for Service Assembly {0}. Cause: Problems have been encountered creating an OpenSymphony Quartz Scheduler. Action: Try cycling the GlassFish Application Server and the Scheduler Binding Component. |
SCHEDBC-7002 |
Critical |
Cannot find respective Scheduler endpoint. Cause: [Rare] JBI framework is probably malfunctioning. Action: Try cycling GlassFish Application Server. |
SCHEDBC-7003 |
Critical |
WSDL for Endpoint {0} does not represent a valid Scheduler binding. Cause: No appropriate Scheduler Binding Component binding WSDL has been found in the Service Unit. Action: Ensure that the respective project involving the Scheduler Binding Component has an appropriate binding WSDL specified and re-deploy the Composite Application project. |
SCHEDBC-7004 |
Critical |
Cannot initialize Scheduler for endpoint {0}. Cause: Cannot initialize the Scheduler for non-specific reasons. Action: Verify the Scheduler Binding Component binding WSDL is correct and re-deploy the Composite Application project. |