JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Alert Codes and Error Messages for Oracle Java CAPS JBI Components     Java CAPS Documentation
search filter icon
search icon

Document Information

JBI Component Alert Codes and Error Messages

BPEL Service Engine Alert Codes

Intelligent Event Processor Service Engine Alert Codes

Java EE Service Engine Alert Codes

XSLT Service Engine Alert Codes

Database Binding Component Alert Codes

File Binding Component Alert Codes

FTP Binding Component Alert Codes

HL7 Binding Component Alert Codes

HTTP Binding Component Alert Codes

JMS Binding Component Alert Codes

LDAP Binding Component Alert Codes

Scheduler Binding Component Alert Codes

XSLT Service Engine Logging Codes

Email Binding Component Logging Codes

HL7 Encoder Logging Codes

POJO Service Engine Logging Codes

Scheduler Binding Component Logging Codes

Component Toolkit Logging Codes

Common Utility Logging Codes

Quality of Service Logging Codes

Runtime Framework Error Messages

Runtime NMR Error Messages

Runtime Management Error Messages

Runtime Management Facade Error Messages

Runtime Application Verifier Error Messages

Runtime Common Client Error Messages

Runtime Utility Error Messages

Runtime Command-Line Interface Error Messages

Runtime Command-Line Interface Error Messages

Common Utility Logging Codes

The following table lists each logging code generated by the Common Utility library and describes the cause of the log message as well as providing a recommended action for you to take.

Logging Code
Severity
Message Text, Cause, and Action
UTIL-4001
Config
Resizing pool: new size={0}

Cause: The Service Assembly descriptor could not be parsed.

Action: Review the server log for more information about the cause of the error and correct the descriptor.

UTIL-6001
Warning
Failed to parse Service Assembly descriptor: {0}

Cause: The Service Assembly descriptor could not be parsed.

Action: Review the server log for more information about the cause of the error and correct the descriptor.

UTIL-6002
Warning
Failed to parse service unit descriptor: {0}

Cause: The service unit descriptor could not be parsed.

Action: Review the server log for more information about the cause of the error and correct the descriptor.

UTIL-6003
Warning
Failed to parse Service Assembly connections: {0}

Cause: The connections in the Service Assembly descriptor are invalid.

Action: Review the server log for more information about the cause of the error, fix the assembly descriptor, and redeploy.

UTIL-6004
Warning
Descriptor file does not exist: {0}

Cause: The service descriptor file is not present at the specified location.

Action: Verify that the service descriptor is packaged with the deployment artifacts.

UTIL-6005
Warning
Failed to parse Identification element: {0}

Cause: The service descriptor identification configuration is invalid.

Action: Review the server log for more information about the cause of the error.

UTIL-6006
Warning
Invalid context, may not be NULL or zero length!

Cause: The component did not provide a correct diagnostic logging context.

Action: File a defect ticket against the component.

UTIL-6007
Warning
Invalid context, must be in key-value pairs!

Cause: The component did not provide a correct diagnostic logging context.

Action: File a defect ticket against the component.

UTIL-6008
Warning
XmlResource failed to create DocumentBuilder: {0}

Cause: A pooled XML resource could not instantiate a DocumentBuilder.

Action: Review the server log for more information about the cause of the error.

UTIL-6009
Warning
XmlResource failed to create Transformer: {0}

Cause: A pooled XML resource could not create a transformer.

Action: Review the server log for more information about the cause of the error.

UTIL-6010
Warning
Failed to convert to DOMSource: {0}

Cause: An XML Source could not be converted to a DOM Document.

Action: Verify the data is correct, and review the server log for more information about the cause of the error.

UTIL-6011
Warning
Failed to reset StreamSource: {0}

Cause: A component was unable to reuse a streamed XML source.

Action: Review the server log for more information about the cause of the error.

UTIL-6012
Warning
Unable to register MBean, forced unregister failed for: {0}

Cause: The MBean was previously registered and failed to unregister.

Action: Uninstall the stale MBean interfering with the current one.

UTIL-6013
Warning
Failed to register MBean {0}: {1}

Cause: An error occurred registering MBean.

Action: Review the server log for more information about the cause of the error.

UTIL-6014
Warning
Failed to unregister MBean {0}: {1}

Cause: An error occurred unregistering MBean.

Action: Review the server log for more information about the cause of the error.

UTIL-6015
Warning
Catalog file not found at {0}!

Cause: Resolver catalog file could not be found in the service unit.

Action: Verify presence of catalog.xml in deployment artifacts and review the server log for more information about the cause of the error.

UTIL-6016
Warning
Failed to resolve catalog base {0} (original base = {1})

Cause: The resolver catalog may be invalid.

Action: Review the server log for more information about the cause of the error.