ESS-05108: The user provided metadata type of {0} does not match the metadata type of {1} in the metadata object id string

Cause: The metadata type specified by the user does not match the metadata type specified by the metadata object id string.

Action: Check the metadata repository to ensure the metadata is correct or specify the correct type and try again.

Level: 1

Type: WARNING

Impact: Other

ESS-05109: While performing a metadata query, the following problem was detected with one of the query results: {1} The query will continue but exclude the piece of metadata with name {0}. This may affect the expected query results.

Cause: A problem occurred while processing a result of the metadata query.

Action: Check the piece of metadata causing the problem for any issues and check the health of the metadata respository.

Level: 1

Type: ERROR

Impact: Other

ESS-05110: An error occurred while retrieving the metadata object with name {0} of type {1}.

Cause: A problem occurred while retrieving a piece of metadata.

Action: See the base exception for the cause then check the piece of metadata causing the problem for any issues and check the health of the metadata respository.

Level: 1

Type: ERROR

Impact: Other

ESS-05490: Service MBeans registration failed.

Cause: Service MBeans registration failed.

Action: Review the log file for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-05700: Failed to obtain a metadata service instance. {0}

Cause: Failed to obtain a metadata service instance.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-05704: An error occured invoking the MetadataService MBean. {0}

Cause: An error occurred invoking the RuntimeService MBean.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05705: Failed to save the {0} with name {1}.

Cause: Failed to save the metadata object.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05706: {0} with name {1} does not exist.

Cause: Unable to find the metadata object.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05707: {0} with name {1} already exists.

Cause: The metadata object already exists.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05708: Failed to delete the {0} with name {1}.

Cause: Unable to delete the metadata object

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05709: Parameter {0} starts with {1} which is a reserved parameter keyword.

Cause: A property defined by the metadata object contains a reserved keyword.

Action: See the base validation exception for the original validation error.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05711: A null value cannot be used when querying the {0} field.

Cause: A value of null was used as the query value.

Action: Provide a non-null argument.

Level: 1

Type: WARNING

Impact: Other

ESS-06000: Failed to obtain a runtime service instance. {0}

Cause: Failed to obtain a runtime service instance.

Action: Review log file for underlying cause.

Level: 1

Type: ERROR

Impact: Other

ESS-06002: Failed to close runtime service handle. {0}

Cause: Failed to close runtime service handle.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06003: Runtime service system failure. {0}

Cause: Runtime service system failure.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06100: No request found for the given id {0}.

Cause: A request was not found in ESS runtime storage corresponding to the indicated request identifier.

Action: Specify a request identifier for an existing request.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-06102: An error occured invoking the RuntimeService MBean.

Cause: An error occurred invoking the RuntimeService MBean.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06521: Failed to start request dispatcher.

Cause: An error occurred while trying to start the request dispatcher.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06522: Failed to start request processor.

Cause: An error occurred while trying to start the request processor.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06523: Failed to start system event service.

Cause: An error occurred while trying to start the system event service.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06524: Failed to start application event service.

Cause: An error occurred while trying to start the application event service.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06525: Failed to start heartbeat monitor.

Cause: An error occurred while trying to start the heartbeat monitor.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06526: Failed to update configuration information.

Cause: An error occurred while trying to update configuration information.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06527: Failed to start deferred monitor.

Cause: An error occurred while trying to start the deferred monitor.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06528: Failed to start work unit worker.

Cause: An error occurred while trying to start the work unit worker.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06530: Dispatcher cannot be started when it is in the {0} state.

Cause: Dispatcher cannot be started when it is in the specified state.

Action: Start the dispatcher when it is in STOPPED state.

Level: 1

Type: WARNING

Impact: Other

ESS-06531: Dispatcher cannot be stopped when it is in the {0} state.

Cause: Dispatcher cannot be stopped when it is in the specified state.

Action: Stop the dispatcher when it is in STARTING or RUNNING state.

Level: 1

Type: WARNING

Impact: Other

ESS-06532: Processor cannot be started when it is in the {0} state.

Cause: Processor cannot be started when it is in the specified state.

Action: Start the processor when it is in STOPPED state.

Level: 1

Type: WARNING

Impact: Other

ESS-06533: Processor cannot be stopped when it is in the {0} state.

Cause: Processor cannot be stopped when it is in the specified state.

Action: Stop the processor when it is in STARTING or RUNNING state.

Level: 1

Type: WARNING

Impact: Other

ESS-06538: No endpoint is available for {0}.

Cause: An application using the specified endpoint application name is not deployed.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06539: Could not create endpoint for {0}.

Cause: An error occurred creating an application endpoint.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06540: Failed to get an endpoint to run dispatcher for application {0}.

Cause: Dispatch monitor was unable to obtain an application endpoint. This may happen when the system is busy and does not necessary indicate a problem.

Action: Review the log file for indications of a problem if this persists.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06541: Error during dispatch for application {0}.

Cause: Error during dispatch for application.

Action: Review the log for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-06542: Error getting applications to dispatch.

Cause: Error getting applications for dispatch.

Action: Review the log for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-06543: Failed to deactivate endpoint for application {0}.

Cause: An error occurred while removing an application endpoint.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06551: Failed processing trigger for {0} event.

Cause: Failed processing event trigger.

Action: Review the log for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06552: Failed processing trigger for {0} event for request {1}.

Cause: Failed processing event trigger.

Action: Review the log for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06553: Failed processing lifecycle for {0} event for request {1}.

Cause: Failed processing lifecycle event for a request.

Action: Review the log for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06557: Failed to start heartbeat worker {0}.

Cause: ESS heart beat monitor failed to start due to a system failure.

Action: Check the causeBy clause of this exception to find more details.

Level: 1

Type: WARNING

Impact: Other

ESS-06558: Failed to get an endpoint to run a heartbeat for application {0}.

Cause: Heartbeat monitor was unable to obtain an application endpoint. This may happen when the system is busy and does not necessary indicate a problem.

Action: Review the log file for indications of a problem if this persists.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06560: Error encountered by event worker.

Cause: Error encountered by event worker.

Action: Review the log for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06570: Failed to get metadata for work assignment {0}.

Cause: Unable to retrieve work assignment metadata when analyzing work assignment bindings. The work assignment is ignored.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06571: Failed to get workshift metadata ({0}) for work assignment {1}.

Cause: Unable to retrieve workshift metadata when analyzing a work assignment binding. The work assignment processing will ignore the workshift.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06572: Failed to get schedule metadata ({0}) for work assignment {1}.

Cause: Unable to retrieve schedule metadata when analyzing a work assignment binding. The work assignment processing will ignore the workshift associated with the schedule.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06573: Failed to start work assignment {0}.

Cause: Unable to start the first worker for the work assignment. The start will be retried in a short time.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06574: Failed to start starvation thread for work assignment {0}.

Cause: Unable to start the starvation worker for the work assignment. The work assignment will be activated without the starvation worker.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06575: Skipping inactive work assignment {0}.

Cause: The work assignment is defined as inactive and is being skipped.

Action: If the work assignment should be active, change it to active and reload work assignment metadata.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06576: Binding default work assignment.

Cause: The default work assignment is being bound because no user-defined work assignments were bound.

Action: No action is necessary.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06577: Skipping inactive workshift {0} for work assignment {1}.

Cause: The workshift is being skipped because it is inactive. It may have an allocation of 0 or a duration of 0.

Action: No action is necessary.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06578: Started work assignment {0}.

Cause: Started the work assignment.

Action: No action is necessary.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06579: Stopped work assignment {0}.

Cause: Stopped the work assignment.

Action: No action is necessary.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06580: Skipping invalid work assignment {0}.

Cause: The work assignment is being ignored because it is invalid.

Action: Check the work assignment and correct the problem. Ensure the work assignment has at least one workshift defined.

Level: 1

Type: ERROR

Impact: Other

ESS-06581: Skipping invalid work assignment binding {0}.

Cause: The work assignment is being ignored because the binding is invalid.

Action: Check the work assignment binding mode and correct the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06582: Skipping completed work assignment {0}.

Cause: The work assignment has completed and will never again become active. It is being skipped.

Action: If the work assignment should not be completed, check the workshift schedules to ensure they are correct and reload work assignment metadata.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06583: Cannot delete bound work assignment {0}.

Cause: A work assignment that is bound may not be deleted.

Action: Unbind the work assignment and then delete it.

Level: 1

Type: WARNING

Impact: Other

ESS-06584: Reloading metadata for work assignment {0}.

Cause: Reloaded the work assignment metadata.

Action: No action is necessary.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06585: Unable to bind work assignment {0} due to invalid workshift {1}.

Cause: In order to bind a work assignment, each of its workshifts must have an allocation of at least one. If the workshift has a schedule, the schedule must be unexpired, and the workshift duration must be > 0.

Action: Fix the workshift and try again to bind the work assignment.

Level: 1

Type: WARNING

Impact: Other

ESS-06586: Work assignment {0} is invalid and cannot be bound.

Cause: To be bound, a work assignment must have at least one workshift and be active. To be bound in exclusive mode, a work assignment must have a non-empty specialization.

Action: Fix the work assignment and try again to bind it.

Level: 1

Type: WARNING

Impact: Other

ESS-06587: Invalid update of a bound work assignment {0}.

Cause: A work assignment that is bound may not be changed to inactive.

Action: Unbind the work assignment and then update it.

Level: 1

Type: WARNING

Impact: Other

ESS-06590: Error encountered by the worker for work assignment {0}.

Cause: Error encountered by worker for work assignment.

Action: Review the log file for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-06592: Error while processing request {0} for application {1}.

Cause: Error while processing request for application

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06593: Required property, {0}, is not present in message received for work assignment {1}.

Cause: Required property is not present in message received for work assignment.

Action: Add the required request property for work assignment.

Level: 1

Type: ERROR

Impact: Other

ESS-06594: Failed to schedule additional work for work assignment {0}. {1}