37 SOA-06000 to SOA-67028

SOA-06000: No processor registered for asynchronous job type: {0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-06001: Skipped recovery attempt for fault {0} : {1}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06002: Recovery attempt for fault {0} failed : {1}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06003: Recovery attempt for fault {0} succeeded

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06004: Exception encountered during recovery attempt: {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06005: The {0} service engine does not support automated fault recovery

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06006: The composite {0} is not in a state for which recovery can be performed.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06007: Fault is unrecoverable

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06008: Incorrect job type: {0} ; Expected {1}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-06009: Scheduled asynchronous job: {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06010: Updated status for asynchronous job {0} : {1}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06011: Recorded results for asynchronous job {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06012: The results for job {0} are not available because the processing has not yet completed.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06013: Processing asynchronous {0} job {1}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06014: The processing of asynchronous job {0} failed: {1} : {2}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06015: {1} faults matched the filter criteria associated with the bulk fault recovery job {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06016: The composite {0} could not be found

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-06017: The Fabric mesh could not be accessed: {0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-06018: Fault state unknown for faultId {0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-06019: operation to retrieve sca entity associated data failed {0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-06020: The scheduling of asynchronous job {0} failed.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-10000: Import type {0} is not currently defined. The only valid import types are "wsdl" and "edl". If you are attempting to import an xsd file, please do so through a WSDL document.

Cause: The import type specified for the composite import is unrecognized

Action: Make sure the import type is one of the currently recognized types (.edl, .wsdl)

Level: 1

Type: ERROR

Impact: Configuration

SOA-10001: No binding node (e.g. <binding.ws>) found for {0}. Please make sure that the composite specifies a binding of a given type.

Cause: No bindings are configured for the given service or reference

Action: Check that the composite's services and references specify at least one binding.

Level: 1

Type: ERROR

Impact: Configuration

SOA-10002: Unable to add a code source to the composite classloader due to an exception. Please ensure that the proper resources are available in the SCA-INF/classes, SCA-INF/gen-classes, and SCA-INF/lib composite archive sub-directories.

Cause: Unable to add a code source to the composite's classloader due to an exception

Action: Ensure that resources are available in the SCA-INF/classes, SCA-INF/gen-classes, and SCA-INF/lib composite archive sub-directories.

Level: 1

Type: ERROR

Impact: Deployment

SOA-10003: Failed to retrieve the application topology node from the TopologyService using {0}.

Cause: Unable to retrieve a toplogy node from the Toplogy Service

Action: Please check whether the toplogy node path is valid

Level: 1

Type: ERROR

Impact: Deployment

SOA-10004: Failed to create MAS-enabled componentType lookup; {0}.

Cause: Unable to create a strategy that enables the lookup of .componentType files in a MAS environment

Action: Make sure the toplogy node path, composite home directory, and strategy class name are correct

Level: 1

Type: ERROR

Impact: Deployment

SOA-10005: Failed to retrieve {0} document from topology node {1}.

Cause: Unable to retrieve a document from the topolgy node

Action: Make sure the toplogy node path, composite home directory, and the document name are correct

Level: 1

Type: WARNING

Impact: Other

SOA-10006: Error occurred while retrieving {0} document from topology node {1}. The underlying cause was a {2}.

Cause: An error occurred during the retrieval of a document from a topology node

Action: Make sure the resource path is valid and that the deployment succeeded

Level: 1

Type: ERROR

Impact: Configuration

SOA-10007: Error occurred while attempting to retrieve message part {0} from a normalized message payload with elements {1}.

Cause: An attemp to retrieve a message part of a given name from a Normalized Message failed

Action: Make sure that there is no mismatch between the WSDL defined part name and a configured part name

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-10008: Error occurred during deployment of component: {0} to service engine: {1}, for composite: {2}

Cause: An error occurred during component deployment

Action: Please check the root cause of the failure

Level: 1

Type: ERROR

Impact: Deployment

SOA-10009: Error occurred during creation of domain/instance noun: {0}

Cause: An error occurred during creating noun for domain/instance

Action: Please check the root cause of the failure

Level: 1

Type: ERROR

Impact: Configuration

SOA-10010: Error occurred while getting portable mbean factory: {0}

Cause: An error occurred while getting portable mbean factory

Action: Please check the root cause of the failure

Level: 1

Type: ERROR

Impact: Configuration

SOA-20000: Message Router for {0} is null. Please validate that the composite deployment completed successfully by checking the server logs.

Cause: There is no message router found for the composite

Action: Check that the composite deployment completed successfully

Level: 1

Type: ERROR

Impact: Deployment

SOA-20001: Message Router for {0} is not able to process messages. The composite state is set to "off". The composite can be turned "on" by using the administrative consoles.

Cause: The composite state or mode do not allow processing of messages

Action: Use the management consoles to set the mode and state of the composite to enable processing

Level: 1

Type: ERROR

Impact: Configuration

SOA-20002: No path info set for provider invocation. Unable to determine composite and service for processing.

Cause: There is no path information in the inovcation URI that facilitates routing of the message to the composite service

Action: Make sure that the invoking URL is of the form http://host:port/soa-infra/services/applicationName/compositeName/serviceName

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20003: Unable to register service.

Cause: There was an issue during the attempt to create the endpoint for the composite service

Action: Make sure that the WSDL either has a service and port that correspond to the values specified in the composite file or that there is no empty service node in the WSDL

Level: 1

Type: ERROR

Impact: Deployment

SOA-20004: Unable to deregister service.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20006: Unable to register reference {0}.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20007: Cannot find binding component for service "{0}".

Cause: There is no binding component configured in the SOA Platform that can handle the given service binding type

Action: Make sure that the binding type specified for the composite's service is valid

Level: 1

Type: ERROR

Impact: Configuration

SOA-20008: Cannot find binding component for reference "{0}".

Cause: There is no binding component configured in the SOA Platform that can handle the given reference binding type

Action: Make sure that the binding type specified for the composite's reference is valid

Level: 1

Type: ERROR

Impact: Configuration

SOA-20009: Cannot find service engine for component "{0}" in composite "{1}".

Cause: There is no service engine configured in the SOA Platform that can handle the given component implmentation type

Action: Make sure that the implementation type specifed for the composite's component is valid

Level: 1

Type: ERROR

Impact: Configuration

SOA-20010: Unable to find Binding Component for type "{0}".

Cause: No binding component found for the given type

Action: Make sure the configured type has a corresponding SOA Platform configured binding component

Level: 1

Type: ERROR

Impact: Configuration

SOA-20011: Unable to find Service Engine for type "{0}".

Cause: No service engine found for the given type

Action: Make sure the configured type has a corresponding SOA Platform configured service engine

Level: 1

Type: ERROR

Impact: Configuration

SOA-20012: Unable to find component or reference identified by "{0}".

Cause: Unable to find a component or reference of the given name in the composite

Action: Make sure the composite wires are properly formed and reference existing components and/or references

Level: 1

Type: ERROR

Impact: Configuration

SOA-20013: MDS Root mis-configuration.

Cause: The MDS root directory is misconfigured

Action: Make sure the composite directories specified in the deployed-composites.xml file are correct

Level: 1

Type: ERROR

Impact: Deployment

SOA-20018: Cannot read WSDL "{0}" from Metadata Manager.

Cause: There was a problem reading a WSDL document from the MDS repository

Action: Make sure the composite imports point to the valid WSDL paths

Level: 1

Type: ERROR

Impact: Deployment

SOA-20019: Object "{0}" does not exist in metadata repository.

Cause: The requested file or resource does not exist in the MDS repository

Action: Make sure the resource path is valid

Level: 1

Type: ERROR

Impact: Configuration

SOA-20020: Deployment of composite "{0}" failed: {1}.

Cause: Unable to deploy the composite

Action: Check the associated exception for more information

Level: 1

Type: ERROR

Impact: Deployment

SOA-20021: Undeployment of composite "{0}" failed: {1}.

Cause: There was an error generated during the undeployment of a composite

Action: Check the associated exception for more information concerning the undeployment issue

Level: 1

Type: ERROR

Impact: Deployment

SOA-20025: Failed to find a WSDL Definition for service: "{0}".

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20026: Failed to find composites to deploy based on path: "{0}".

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20027: Unable to create interceptors, InterceptorChainFactory may not be defined for "{0}".

Cause: There was a problem creating an interceptor chain associated with the composite

Action: Make sure that the interceptor chain factories are configured in the SOA platform's configuation file located in the fabric war's WEB-INF directory

Level: 1

Type: ERROR

Impact: Deployment

SOA-20028: Unable to create mbeans for the composite "{0}" because of error "{1}".

Cause: There was an error generated during the creation of the composite MBean

Action: Check the associated exception for the cause of the error

Level: 1

Type: ERROR

Impact: Deployment

SOA-20029: Unable to unregister mbean for the composite "{0}" because of error "{1}".

Cause: There was an error while attempting to unregister the composite MBean

Action: Check the associated exception for the cause of the error

Level: 1

Type: ERROR

Impact: Deployment

SOA-20030: Unable to unregister deployed composites runtime mbean because of error "{0}".

Cause: There was an error while attempting to unregister the deployed composites MBean

Action: Check the associated exception for the cause of the error

Level: 1

Type: ERROR

Impact: Deployment

SOA-20031: An active composite for "{0}" has already been registered. Only one active composite is allowed.

Cause: An attempt was made to deploy an active composite for an application that already has an active composite

Action: Make sure that only one active composite is associated with a given application. You can deactive/activate composites via the management consoles

Level: 1

Type: ERROR

Impact: Deployment

SOA-20032: The composite "{0}" is retired. New instances cannot be initiated.

Cause: An attempt was made to initiate a composite instance using a retired composite

Action: Make sure to create a new instance with an active composite. The composite mode can be configured via the management consoles

Level: 1

Type: ERROR

Impact: Deployment

SOA-20034: No composite found for application "{0}", composite name "{1}" and revision "{2}".

Cause: An attempt was made to reload a composite application for which resources can not be found in the metadata repository

Action: Make sure that the application name, composite name, revision, and label specify a valid metadata store

Level: 1

Type: ERROR

Impact: Configuration

SOA-20035: Composite "{0}" has already been loaded.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20036: Composite "{0}" has been loaded.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20037: Composite home directory "{0}" does not exist.

Cause: The composite home directory specified is not valid

Action: Make sure the composite home directory specified in deployed-composites.xml is valid

Level: 1

Type: ERROR

Impact: Deployment

SOA-20038: Composite "{0}" does not exist.

Cause: No composite message router was found for the specified composite

Action: Make sure the composite distinguished name specified is valid and that the composite application deployed successfully

Level: 1

Type: ERROR

Impact: Deployment

SOA-20039: Operation not supported.

Cause: An attempt was made to undeploy using the deployment update mechanism

Action: N/A

Level: 1

Type: ERROR

Impact: Deployment

SOA-20040: Message exchange pattern not currently supported.

Cause: The attempted message exchange pattern is not supported

Action: Make sure that the composite wiring is valid

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20041: Deployment failure on rollback: {0}

Cause: An error was raised during an attempt to rollback a composite deployment

Action: Make sure that all composite resources have been removed

Level: 1

Type: ERROR

Impact: Deployment

SOA-20042: Not enough information to ascertain composite name from pathInfo "{0}".

Cause: The path information in the URI was not sufficient enough to identify a composite

Action: Make sure that the URL used to invoke the composite service has the proper application name, composite name, revision, and label

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20043: No deployed composite found for path "{0}".

Cause: The path information in the URI was not sufficient enough to identify a composite

Action: Make sure that the URL used to invoke the composite service has the proper application name, composite name, revision, and label

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20044: Unable to retrieve resource "{0}" associated with composite "{1}".

Cause: An attempt to retrive a composite application associated resource (e.g. a WSDL file) failed

Action: Make sure the URL specified is correct

Level: 1

Type: ERROR

Impact: Deployment

SOA-20045: No WSDL URL provided

Cause: No WSDL URI was specified for the composite associated WSDL

Action: Make sure the WSDL import in the composite file is valid and specifies a URI for the file

Level: 1

Type: ERROR

Impact: Deployment

SOA-20046: Deployment of MBEANS for composite "{0}" failed: {1}.

Cause: There was a problem deploying the composite MBeans

Action: Check the associated exception for more information. There may have been a problem deregistering the MBean during a previous undeployment.

Level: 1

Type: ERROR

Impact: Deployment

SOA-20047: Unable to initialize composite parser: {0}.

Cause: Unable to initialize the composite parser

Action: Make sure that any parser providers registered in the fabric war web.xml file are valid

Level: 1

Type: ERROR

Impact: Configuration

SOA-20048: Unable to discover local host name: {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20049: Unable to register composite loader due to exception: {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20050: Binding components failed to create holder type for {0}.

Cause: The required holder class is not available on the classpath

Action: Make sure the holder class is available in the classpath

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20051: Return value from the Java Service method {0} is invalid.

Cause: The service returned a value of a different type than was expected

Action: Verify that the service and the WSDL correspond

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20052: Binding Component failed to access holder value for {0}.

Cause: Unable to call a setter/getter on the holder class instance

Action: Make sure the access method is public

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20053: Binding Component is unable to locate operation {0} for java service {1}.

Cause: The requested method does not exist on the target service class

Action: Verify that the target service implements all methods defined in the WSDL

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20054: Binding Component failed to invoke method {0}.

Cause: The requested method of the target service is not public

Action: Verify that the targets service's methods are public

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20055: Missing WebResult method annoation for java service {0}.

Cause: The @WebResult annotation is not defined for the service interface

Action: Make sure the @WebResult annotation is specified in the service interface

Level: 1

Type: ERROR

Impact: Programmatic

SOA-20056: Could not locate service for {0}.

Cause: The requested service is not registered

Action: Make sure the service is registered and named correctly

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20057: Could not find invocation context containing sdo metadata for component {0}.

Cause: The requested service is not registered

Action: Make sure the service is registered and named correctly

Level: 1

Type: ERROR

Impact: Deployment

SOA-20058: Could not find registry for {0}.

Cause: The requested service registry does not exist

Action: Make sure that the registry is available and named correctly

Level: 1

Type: ERROR

Impact: Deployment

SOA-20059: Unable to copy the WSDL definition due to exception

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20060: Partname metadata for the parameter {0} is missing.

Cause: A parameter of a method of the service interface is missing the @PartName annotation

Action: Make sure the @PartName annotation is specified for the parameters of the method

Level: 1

Type: ERROR

Impact: Programmatic

SOA-20061: Input argument {0} has a wrong parameter java type.

Cause: Unable to create an instance of a parameter value

Action: Make sure the parameter classes are available and have default constructors

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20097: Binding component is unable to load schema from this location: {0}

Cause: Could not load an imported schema

Action: Make sure the schema is available in the location specfied in the WSDL

Level: 1

Type: ERROR

Impact: Deployment

SOA-20098: Binding component failed to initialize.

Cause: There was an internal error during initialization

Action: Please contact support

Level: 1

Type: ERROR

Impact: Deployment

SOA-20099: WSDL port metadata in composite {0} not found

Cause: There was an internal error during load

Action: Please contact support

Level: 1

Type: ERROR

Impact: Deployment

SOA-20100: Binding component failed to register Metadata types with SDO provider.

Cause: There was an internal error during load

Action: Please contact support

Level: 1

Type: ERROR

Impact: Deployment

SOA-20101: Metadata for operation {0}, service {1} can not be found.

Cause: The operation was not defined in the service WSDL

Action: Make sure the operation is defined in the service WSDL

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20102: An error occurred while scheduling deployment. Exception reported is "{0}"

Cause: There was an error while attempting to schedule a deployment

Action: Check the associated exception for the cause of the error

Level: 1

Type: ERROR

Impact: Deployment

SOA-20104: The composite for model "{0}" is not found!

Cause: There was an error during retrieval of the service associated composite

Action: Make sure the composite is valid

Level: 1

Type: ERROR

Impact: Configuration

SOA-20106: Binding Component is unable to load schema at "{0}" due to missing system id in the referencing source schema.

Cause: Unable to load schema due to missing system id in the referencing WSDL or schema

Action: Ensure the system id is defined in the WSDL

Level: 1

Type: ERROR

Impact: Deployment

SOA-20107: Configuration Error in Java Binding. Unable to find portType or interface.

Cause: Service or port names were not specified in the binding configuration

Action: Make sure the service and port name are available in the binding configuration

Level: 1

Type: ERROR

Impact: Configuration

SOA-20108: The resource "{0}" not found in the composite "{1}"

Cause: Unable to retrieve a resource from the composite's MDS repository

Action: Make sure the resource path specified, relative to composite URI, is correct

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20109: Invocation Exception: {0}:

Cause: The service generated an error during invocation

Action: Ensure that the service is operating correctly

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20110: This {0} method is not implemented!

Cause: One way operations are not supported for SDO dynamic stubs

Action: Consider using an alternate message exchange pattern

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20111: Binding Component failed to create user defined faults.

Cause: A SOAP fault was generated by the service invocation

Action: Ensure that the service is operating properly. The fault may be expected.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20112: The called service raised a fault.

Cause: The service generated an exception

Action: Ensure that the service is operating properly

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20113: Unable to access the following endpoint(s): {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20114: Unable to update reference instance with response payload due to exception

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20115: Illegal modification to existing composite {0}. Changes are not allowed to elements of the composite distinguished name (application name, composite name, revision, and label). If you are attempting a re-deployment of a failed deployment, please undeploy and then deploy the composite.

Cause: The attempted change of the deployed composite file was not valid

Action: Make sure the change you are making is allowed

Level: 1

Type: ERROR

Impact: Deployment

SOA-20116: Only changes to policy references of {1} of composite {0} are supported by the Web Service Binding Components. All other changes (e.g. changes to the port attribute of a binding) will be ignored.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20117: The wire target URI {1}/{2} for composite {0} is not valid. No service {2} is defined for component {1} in its componentType file. Please check the componentType file for component {1} for valid service names.

Cause: The composite wire appears to be malformed since no such component/service pair exists

Action: Please check the componentType file for the component for valid service names.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20118: The wire source URI {1}/{2} for composite {0} is not valid. No reference {2} is defined for component {1} in its componentType file. Please check the componentType file for component {1} for valid reference names.

Cause: The composite wire appears to be malformed since no such component/reference pair exists

Action: Please check the componentType file for the component for valid reference names.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20119: Unable to find a WSDL that has a definition for service {0} and port {1}. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.

Cause: Unable to find a WSDL that has a definition corresponding to the provided service and port names

Action: Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.

Level: 1

Type: ERROR

Impact: Deployment

SOA-20120: Unable to find a composite definition in {0}. Please make sure there is a composite.xml definition file that defines a composite with the same name as the composite name in the composite JAR name.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20121: An attempt was made to deploy a composite ''{0}'' that has already been deployed. This is an internal error, and does not require any action. The original composite definition remains in effect.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20122: Unable to find a file named ''adf-config.xml'' in the search path starting at {0}. The ''adf-config.xml'' file is required to configure the MDS instance used for composite deployment. Repackage the composite application, providing an MDS store a and namespace named after the composite name.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20124: Unable to process the MDS configuration at {0}. Please verify the formatting and contents of the ''adf-config.xml'' file. Also, check the rest of the log for MDS failures, which could help point out the root cause of the processing failure.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20125: Cannot create an XSLT transformer. Please ensure that your JAXP environmentis properly configured with an XSLT 1.0 transformer.

Cause: Unable to create the adf-config xml transformer

Action: Make sure the adf-config file is property formatted

Level: 1

Type: ERROR

Impact: Deployment

SOA-20126: Updating MDS configuration at {0} with file-based MDS root {1}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20127: Exception when processing MDS configuration.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20128: The context header qname is invalid or malformed. Please check that the correct context header qname is specified for the contextHeadersQNames property in the fabric-config.xml file

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20129: Could not create a context header due to exception

Cause: Unable to create the context header

Action: Ensure that the context provider implementation is valid and working

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20130: Entry Binding Component: invocation of service {0}, operation {1}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-20131: External Binding Component: invocation of service {0}, operation {1}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-20132: Binding Component found port type: {1}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-20133: Binding Component registered the following schema with SDO implementation within context of classloader {1} ==> {0}

Cause:

Action:

Level: 32

Type: TRACE

Impact: Other

SOA-20134: No annotation found on service interface.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20135: Exception creating JAXWS servant. Exception: {0}, Message: {1}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20136: WS Binding: exception during SOAP invocation: {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20138: No oracle-archive.xml found; will use file scanning for application ''{0}''

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20139: Unable to find a registered server for pathInfo {0}. Please ensure that the given composite is deployed. If this is occurring during the processing of a callback, please make sure that the "#" delimiter in the callback URL is properly encoded.

Cause: The path provided in the invocation URI does not map to a deployed composite

Action: Make sure the URI is correct and references a deployed composite application

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20141: Schema validation failed for message part {0}. Please ensure at the message sender level that the data sent is schema compliant.

Cause: Validation of the message part against its schema failed.

Action: Please take actions at the message sender to ensure that the data is schema compliant.

Level: 1

Type: ERROR

Impact: Data

SOA-20143: Unable to register a service endpoint for a defined reference callback. Please ensure the WSDL and reference configuration are correct.

Cause: Unable to register a callback endpoint for the defined reference callback

Action: Make sure that the application configuration is correct. For example, ensure that the associated WSDL does not have any mis-spelled message names.

Level: 1

Type: ERROR

Impact: Configuration

SOA-20144: Unable to find a target component or reference based on invocation context {0}. Please check the composite file and make sure a wire exists for the specified reference or source URI.

Cause: Unable to find a wire for the reference

Action: Make sure that the service or component reference is actually wired to a target

Level: 1

Type: ERROR

Impact: Deployment

SOA-20145: The serviceName/serviceID attribute is missing.

Cause: Unable to find serviceName attribute for the binding

Action: Make sure that the serviceName is specified in the composite

Level: 1

Type: ERROR

Impact: Deployment

SOA-20146: Unable to deploy service {0} with multiple WS bindings. Please make sure there is only one WS binding for the given service in the composite file.

Cause: Unable to deploy a service with multiple WS bindings

Action: Make sure that the service has only one WS binding

Level: 1

Type: ERROR

Impact: Deployment

SOA-20147: javaInterface name for the binding is missing or the interface class is not available.

Cause: Unable to find javaInterface attribute for the binding

Action: Make sure that javaInterface attribute is specified on the composite

Level: 1

Type: ERROR

Impact: Deployment

SOA-20148: null

Cause: Failure in looking up EJB

Action: Make sure JNDI properties, jndi name specified are correct.

Level: 1

Type: ERROR

Impact: Deployment

SOA-20149: Caller is not in allowed role!

Cause: Failure in authenticating ejb invocation

Action: Make sure invocation client has the right role mapped.

Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20150: SOA EJB Invoker could not load bean interface class defined for service {0}.

Cause: Failure in loading ejb interface class

Action: Make sure interface class is included in the deployment package.

Level: 1

Type: ERROR

Impact: Deployment

SOA-20151: SOA EJB Invoker could not locate composite for service {0}.

Cause: Failure in locating composite

Action: Make sure the composite configuration is correct

Level: 1

Type: ERROR

Impact: Configuration

SOA-20152: SOA EJB Invoker could not locate method named {0} with {1} of arguments on interface class {2} for service.

Cause: Failure in locating method

Action: Make sure the composite configuration is correct

Level: 1

Type: ERROR

Impact: Configuration

SOA-20153: Failure in processing jps credential store properties, exception stack: {0} .

Cause: Failure in processing credential store properties

Action: Make sure the properties are specified correctly or permission to access the the store has been setup.

Level: 1

Type: ERROR

Impact: Configuration

SOA-20154: The path "{0}" has already been used by another direct binding. Please select a different path override.

Cause: Illegal pathOverride used in composite configuration. The alias name has already been used for other another direct binding.

Action: Select a different path alias for the direct binding component.

Level: 1

Type: ERROR

Impact: Configuration

SOA-20155: Expected protocol ''soadirect'', got ''{0}'' instead.

Cause: Illegal protocol used in direct binding composite configuration.

Action: Correct path should start with "soadirect"

Level: 1

Type: ERROR

Impact: Configuration

SOA-20156: Invalid service path "{0}".

Cause: Service Path used in the invocation is invalid.

Action: Correc the service path.

Level: 1

Type: ERROR

Impact: Configuration

SOA-20157: Service not found for path "{0}".

Cause: Service not found for the path name used in the invocation.

Action: Check composite configuration to see if the path name used matches.

Level: 1

Type: ERROR

Impact: Configuration

SOA-20158: Direct binding component failed to initialize.

Cause: Exception occured during the direct binding component initialization.

Action: Check the exception for detailed failure cause.

Level: 1

Type: ERROR

Impact: Configuration

SOA-20159: Direct binding component not initialized.

Cause: Direct binding component has not been initialized.

Action: Check server startup log to see any detailed exception log.

Level: 1

Type: ERROR

Impact: Configuration

SOA-20160: Could not obtain keystore location or password

Cause: Could not obtain the keystore location or password for setting up 2 Way SSL

Action: Make sure that the keystore is available in the default location or is specified in the SOA configuration. In addition, make sure the keystore password is configured in the credential store.

Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-20161: Unable to create SSL Socket Factory

Cause: Could not create the SSLSocketFactory for supporting 2 Way SSL

Action: Check the associated exception for the cause of the failure.

Level: 1

Type: ERROR

Impact: Network

SOA-20168: Could not find a port for the dynamic reference given service name {0} and port type {1}

Cause: Could not find a port that matched the supplied service name and port type for the dynamic reference

Action: Check the dynamic reference configuration and the supplied WSDL to ensure proper configuration.

Level: 1

Type: ERROR

Impact: Configuration

SOA-20169: Folder {0} is not able to process messages. The folder state is set to "off". The folder can be turned "on" by using the administrative consoles.

Cause: The folder state or mode do not allow processing of messages

Action: Use the management consoles to set the mode and state of the folder to enable processing

Level: 1

Type: ERROR

Impact: Configuration

SOA-20170: Partition {0} does not exist. Make sure the partition was created and exists.

Cause: The folder can not be found

Action: Check the folder name and make sure such a folder was created and exists

Level: 1

Type: ERROR

Impact: Configuration

SOA-20171: Cannot find port type {0} in the WSDL. Make sure the port type is defined in the WSDL

Cause: The port type cannot be found

Action: Check the WSDL and make sure the port type is defined in the WSDL

Level: 1

Type: ERROR

Impact: Configuration

SOA-20172: No source URI specified for the given invocation or callback. Please make sure there is a wire specified for the context {0}.

Cause: No source URI for the wire

Action: Check the composite and make sure a wire is defined for the interaction.This is most likely an indication of an error in the wiring.

Level: 1

Type: ERROR

Impact: Configuration

SOA-20173: @WebService or @PortableWebService annotation is required, but not found on {0}.

Cause: Interface class does not contain @WebService annoation.

Action: Add @WebService annotation that describes the service in the interface class.

Level: 1

Type: ERROR

Impact: Configuration

SOA-20174: Failed to get application helper context using service id ''{0}''.

Cause: Unable to create application helper context.

Action: Check the underlying cause from the SDO implementation.

Level: 1

Type: ERROR

Impact: Programmatic

SOA-20175: Binding property {0} overridden by a message property of the same name.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20176: Both csf-key and username/password have been set. The csf-key will be used for authentication processing.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20177: Could not lookup the service endpoint from UDDI either due to a UDDI connection error or the provided ServiceKey {0} was invalid.

Cause: Could not lookup service endpoint from UDDI. Either by error on UDDI connection or invalid ServiceKey

Action: Check the OSR-UDDI inquiryUrl configuration and the supplied ServiceKey to ensure proper configuration.

Level: 1

Type: ERROR

Impact: Configuration

SOA-20178: Unsupported interface type: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20179: Ejb Binding is not found.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20180: Unable to load interface class {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20181: Unknown service: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20182: JNDI name {0} already exists.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20183: Could not find method {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20184: Ejb Reference binding failed to invoke ejb.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20185: Ejb Reference binding failed to create jndi initial context.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20186: No ejb registered with the jndi name: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20187: Invalid EJB2 beans. Create method returned null for : {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20188: Failed to invoke create method on the bean.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20189: Invalid bean. EJB2 reference does not implement Home interface.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20190: Unable to register JNDI binding.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20191: Unable to unregister JNDI binding.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20192: No response for invocation.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20193: Conversion of BizFault failed.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20194: Java based Ejb service binding started a transaction.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-20195: Java based Ejb service binding committed the transaction.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-20196: Java based Ejb service binding rollback the transaction.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-20197: Failed to initialize ADR home directories.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20206: Failed to register SOA diagnostic dumps, DFW (diagnostic framework) not available.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20207: Failed to deregister SOA diagnostic dumps, DFW (diagnostic framework) not available.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20208: Failed to deregister SOA diagnostic dumps, local soa dumps registry not available.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20209: No MBean server found, can not register SOA dump: soa.env.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20210: Can not find facade locator, the following SOA diagnostic dumps not registered: {0}, {1}, {2}.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20211: Failed to look up SOA data source: jndi = [{0}], soa.db dump can not be registered.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20212: SOA data source not available (NULL), soa.db dump not registered.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20213: JNDI context not available, can not look up SOA data source, no DB dump (soa.db) registration.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20214: Not registering SOA incident rules file.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20215: Not unregistering SOA incident rules file {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20216: Not registering custom incident rules file {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20217: Not unregistering custom incident rules file {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20265: No binding found for reference [{1}] of composite [{0}]. A callback endpoint can not be created. Please make sure the composite is deployed to this server.

Cause: There is no reference binding available or deployed

Action: Check that the composite deployment completed successfully and is targeted for this server.

Level: 1

Type: ERROR

Impact: Deployment

SOA-20266: The composites {0} failed during server startup. Please check the logs for more information.

Cause: Composites failed in deployment during server restart

Action: Check the associated exception for more information

Level: 1

Type: ERROR

Impact: Deployment

SOA-20273: Failed to activate weblogic config changes. FailureException: {0}, Failure Message: {1}. {2}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20274: Failed to cancel pending weblogic onfig changes. Failure Message: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20275: Failed to initialize FolderAppRoleManager. Partition specific soa roles will not be created. Failure: {0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20277: An error occurred while creating the application role named [{0}].

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20278: An error occurred while looking up local jndi edit config mbean. {0}

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-20279: An error occurred looking up workmanager named [{0}], use workmanager named [{1}] instead.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20280: Created workmanager named [{0}]

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20281: Error occurred while destroying a partition.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20282: Approle [{0}] for the folder already exists. It will be deleted and recreated.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20283: Failed to lookup soainfra application name, using [soa-infra] instead.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20284: Failed to set AppSecurityContext id to soa application.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20285: JAXBConfigPersistenceHandler is null. WorkManagerGroup configuration changes will not be persisted.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-20286: FolderAppRoleManager was not initialized properly. Partition roles will not be created.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20287: Failed to readjust workmanager MaxThreadsConstraint based on soa datasource max capacity size.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20289: Cannot find the capacity constraint named [{0}] in the domain.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20290: Default SOA WorkManager is used for {0} work execution since the partition workmanager is not available. {1}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20291: SOA Executor WorkManager work with id [{0}] has been rejected. {1}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20298: Error caught when registering SOA dump: [{0}], error message: [{1}], stacktrace: [{2}]

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20304: Failed to look up SOA data source: jndi = [{0}], soa.edn registered but not able to capture diagnostic in DB.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20305: JNDI context not available, can not look up SOA data source, soa.edn registered but not able to capture diagnostic in DB.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20306: SOA data source not available (NULL), soa.edn registered but not able to capture diagnostic in DB.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20307: Invalid format used for the cluster operation message.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20309: Failed to process workmanager group cluster notification message for [{0} {1} operation].

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20311: Failed to activate max thread configuration update. A restart will be necessary.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20315: Failed to save rejected message for service [{0}] of binding type [{1}].

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20317: Failed to invoke health check on startup.

Cause: Could not invoke health check

Action: Contact Oracle support.

Level: 1

Type: WARNING

Impact: Other

SOA-20318: On startup, health check id {0} passed for category ''{1}''. Ran {2} checks.

Cause: Health check completed successfully

Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20319: On startup, health check id {0} passed with warning(s) for category ''{1}''. Ran {2} checks. Number of warnings={3}.

Cause: Health check completed with warning

Action: Check the health check result for details.

Level: 1

Type: WARNING

Impact: Other

SOA-20320: On startup, health check id {0} did not pass for category ''{1}''. Ran {2} checks. Number of errors={3}, warnings={4}, failures={5}.

Cause: Health check completed with error

Action: Check the health check result for details.

Level: 1

Type: ERROR

Impact: Other

SOA-20321: On startup, health check id {0} failed for category ''{1}''. Ran {2} checks. Number of failures={3}, errors={4}, warnings={5}.

Cause: Health check failed to complete

Action: Check the health check result for details.

Level: 1

Type: WARNING

Impact: Other

SOA-20323: SOA server is in quiesce mode - incoming requests will be persisted and processing will be resumed when server is back in running mode.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-20324: Tenant not found with the specified id: {0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-20325: Tenant not found with the specified name: {0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-20327: On startup, there were no health check in category ''{0}'' that could be run.

Cause: Health check was not run since all checks were disabled or not applicable.

Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20329: The size of the requested audit trail for flow id "{0}" is larger than the configured threshold of "{1}" characters.

Cause: The size of the audit trail is larger than the configured threshold.

Action: If the resources are available, increase the instanceTrackingAuditTrailThreshold attribute of the AuditConfig MBean to view this audit trail.

Level: 1

Type: WARNING

Impact: Configuration

SOA-20330: TenantManager instance did not return a valid partition directory.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-20331: URL resolver properties loaded from {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-20332: Unable to load url resolver properties from {0}. Exception: {1}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20333: No tenant partition directory is found. Token updates are not saved.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20334: No domain config directory is found. Token updates are not saved.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20335: Unable to discover cluster info. Exception:

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20336: null

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20337: null

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20338: Variable {0} is not found in the token configuration.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-20339: Unable to find server SelfTuning Mbean instance.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20340: Unable to find soainfra application deployment mbean instance.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20341: Unable to find resource group named ''{0}''.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20342: Unable to find edit session named ''{0}''.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20343: Found an invalid token "{0}". Invalid tokens will not be used for token url replacement.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20344: Failed to register soa datasource listener. DataSource capacity change will not be monitored. Failure: {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20345: Warning: MBean "{0}" has failed to register.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20346: Warning: failed to unregister mbean. {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20347: Warning: failed to find mbean matching {0}.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-20348: Encountered an unexpected failure in the SOA debugger module. This failure should not affect the execution of the composite instance, however, the SOA debugger may not function correctly.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-21500: Error occurred when creating target MDS instance.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21501: Error occurred when rolling back MDS label.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21502: Error occurred when creating MDS label.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21503: MDS store of namespace {0} does not have versioning support. Cannot be used in MAS based deployment.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21504: Only single composite is supported in a SAR archive.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21505: Invalid composite name in undeploy: {0}, both composite name and revision need to be specified.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21506: Cannot find revision in undeploy : {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21507: Error reading deployed-composites.xml.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21508: Cannot find composite deployment coordinator.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21509: Error in reading data from deployer client.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21510: There was an error deploying the composite on {1}: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21511: Cannot find archive: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21512: Data transfer error in MDS.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21513: Command {0} not supported.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21514: MDS Transfer directory {0} already exists for composite {1}. Removing and replacing to deploy new version of composite.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-21515: Cannot find composite {0} in sar file : {1}. Abort deployment.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21516: Cannot find base composite for: {0}. Abort redeployment.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21517: Composite with same revision ID already exists: {0}. Please set the overwrite flag or use different revision ID. Abort deployment.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21518: Protocol {0} is not supported. Only http is supported.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21519: Error parsing composite {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21520: Cannot find shared data archive: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21521: Error removing archive data from MDS for composite: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21522: Error occurs in applying deployment plan {1} to sar file: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21523: Composite {0} cannot be automatically set as default due to state: {1} or mode: {2}. The state needs to be on and the mode needs to be active.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-21524: Error occurred in processing sar file {0} before transferring into MDS store. Please make sure the sar file is a valid jar file.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21525: Cannot find JPS context: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21526: Error occurs in checking JPS role.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21527: User {0} does not have the privilege of deploying/undeploying composites. Only users of SOAAdmin/SOAOperator role are authorized to deploy/undeploy composites.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21528: There was an error undeploying composite on {1}: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21529: There was an error deploying/undeploying composite on {1}: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21530: CompositeDeploymentServlet-----> received request from user: {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21532: CompositeDeploymentServlet initialized.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-21533: User [{0}] has been successfully authorized.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21534: Start unzipping data to base directory: {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21535: Complete unzipping data.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21536: Calling DeployManager to attach deployplan: {0} to SAR file: {1}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21537: Sending back error message: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21538: Removing temporary directory: {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21539: Perform deployment operation with redeploy flag: {0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-21540: Perform undeployment operation: {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21541: Calling coordinator to undeploy {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21542: Undeploying revision: {0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-21543: Deploying SAR file: {0} to domain: {1}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21544: Deploying shared data file: {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21545: Calling coordinator to deploy {0}, with isForceDefault flag: {1}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21546: Calling coordinator to update composite. base composite: {0}, new composite: {1}, isForceDefault flag: {2}, keepInstancesOnRedeploy flag: {3}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21547: AutoDeployer-> starting deploying shared data file: {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21548: AutoDeployer-> shared data file {0} was successfully deployed. Time spent: {1} sec. This file will be removed.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21549: AutoDeployer-> starting deploying SAR file: {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21550: AutoDeployer-> SAR file {0} was successfully deployed. Time spent: {1} sec. SAR file will be removed.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21551: AutoDeployer-> removing temporary MDS data directory {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21552: Preparing transferring data into MDS for package: {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21553: Transferred data into MDS successfully for package: {0}. Transferred size: {1}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21554: Removed extra data from MDS successful for package: {0}. Removed size: {1}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21555: Preparing removing data from MDS for package: {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21556: Removed data from MDS successfully for package: {0}. Removed size: {1}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21557: CompositeDeploymentServlet-----> completed deploying {0} successfully. Time spent: {1} sec.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21558: CompositeDeploymentServlet-----> completed undeploying {0} successfully. Time spent: {1} sec.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21559: CompositeDeploymentServlet-----> completed redeploying {0} successfully. Time spent: {1} sec.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21560: Cannot remove temporary directory: {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-21562: Composite from sar file: {0} already exists in the target server. Will NOT attempt redeployment and this sar file will be removed from the autodeploy directory.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21563: The composite ({0}) imported a shared library: {1}/{2}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21564: The classloader for the shared library ({1}/{2}) referenced by the composite ({0}) cannot be found.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-21566: There was an error exporting composite on {1}: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21567: Sending back jar file: {0} of length: {1}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21568: CompositeDeploymentServlet-----> completed exporting composite {0} successfully. Time spent: {1} sec.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21569: CompositeDeploymentServlet-----> completed exporting post deployment updates {0} successfully. Time spent: {1} sec.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21570: CompositeDeploymentServlet-----> completed importing post deployment updates {0} successfully. Time spent: {1} sec.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21571: There was an error exporting post deployment changes on {1}: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21572: There was an error importing post deployment changes on {1}: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21573: CompositeDeploymentServlet-----> completed exporting shared data of pattern {0} successfully. Time spent: {1} sec.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21574: There was an error exporting shared data on {1}: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21575: adf-config.xml file cannot be null.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21576: Cannot find adf-config file: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21577: Cannot get adf-config file URL: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21578: Cannot create SOA MDS instance.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21579: Cannot find composite: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21580: Cannot find deployed-composites.xml.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21581: The composite name in composite.xml of the jar file: {0} does not match the composite name to be updated: {1}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21582: The composite revision in composite.xml of the jar file: {0} does not match the composite revision to be updated: {1}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21583: Composite does not exist, cannot import updates: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21584: Composite label cannot be null: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21585: Error read deployed-composites.xml: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21586: Cannot find deployed-composites.xml to save.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21587: Cannot update deployed-composites.xml.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21588: There was an error removing shared data on {1}: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21589: CompositeDeploymentServlet-----> completed removing shared data of folder {0} successfully. Time spent: {1} sec.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21590: Error occurred when modifying the revision in composite.xml.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21591: Cannot find Fabric lifecycle: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21592: SOA platform is not fully started. Please retry later.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21593: Calling coordinator to deploy resource files.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21598: Calling coordinator to patch composite {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21601: Calling coordinator to process pre-deployment hook {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21618: MbeanDeployer-> starting deploying SAR file: {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21619: MbeanDeployer-> SAR file {0} was successfully deployed. Time spent: {1} sec.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21620: Notify shared data update.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-21621: CompositeDeploymentServlet-----> completed updating shared data successfully. Time spent: {0} sec.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21622: Notify resource bundle update.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-21623: CompositeDeploymentServlet-----> completed updating resource bundle successfully. Time spent: {0} sec.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21800: Merge tools failed: {0}. Please check log file for more information.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21801: Cannot find merge tool registration file: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21802: Cannot parse mergetool-registry.xml.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21803: Please use JDeveloper to customize the composite of new revision before merge, since the composite of previous revision had been customized.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21804: Invalid target found when creating BindingContainerProxy, target::{0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21805: Invalid target type when calling {0}, instance::{1}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21806: Error building composite model from: {0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21807: ReferenceConfigModel not available for key={0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21808: Invalid inputs, difference in reference entries found original composite.xml {0} DT@RT composite.xml {1}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21809: Exception [{0}] when creating composite model serializer, exception message: {1}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21810: Error [{0}] when creating composite model serializer, error message: {1}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21811: Error [{0}] when marshaling composite model into XML, error message: {1}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21812: Can not create the merged composite.xml file at path={0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21813: Exception when write to merged composite.xml at path={0}, exception=[{1}]

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21814: Invalid target found when creating PolicyReferenceContainerProxy, target::{0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21815: Invalid target found when creating PropertyContainerProxy, target::{0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21816: Invalid location for composite application, it must be a directory where artifacts of the composite reside, the parameter is [{0}]

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21817: Missing directory where the resulted composite.xml will be written...

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21818: Exception when parsing composite.xml: e={0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21819: Inconsistency found between v2 and the result composite.xml regarding callbacks in {0} with key = {1}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21820: Inconsistency found between v1 and DT@RT composite.xml regarding callbacks setting, parent type=[{0}], key={1} in v1 composite.xml has callback : {2}, in DT@RT composite.xml has callback {3}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21821: Inconsistent binding configuration detected between v1 composite.xml and DT@RT composite.xml, binding in v1:[{0}], binding in DT@RT:[{1}].

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21822: Inconsistency found between v1 and DT@RT composite.xml regarding services setting, service[key={0}] in v1 composite.xml {1}, in DT@RT composite.xml {2}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21823: Inconsistency found between v1 and DT@RT composite.xml regarding components setting, component[key={0}] in v1 composite.xml {1}, in DT@RT composite.xml {2}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21824: Missing composite.xml for [{0}]

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-21825: No merge operation, the composite.xml containing DT@RT customization does not present at [{0}].

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21826: Cannot find composite sar file: {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21827: File: {0} is not a composite sar file because composite.xml is not found in this file.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21828: No merge operation, the sensor.xml containing DT@RT customization does not present at [{0}].

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21829: No merge operation, the sensorAction.xml containing DT@RT customization does not present at [{0}].

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22000: The shared library "{0}" is not deployed; Thus, it cannot be redeployed

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-22001: The shared library "{0}" is already deployed

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-22002: Deploying new shared library: {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22003: Redeploying shared library: {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22004: Found shared library "{0}" in the MDS repository

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-22005: Found version {1} of shared library "{0}" in the MDS repository

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-22006: {0} was removed from the MDS repository

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22007: {0} was not removed from the MDS repository

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-22008: {0} was not removed from the MDS repository (It may not be empty)

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-22009: Failed to remove shared library {0}/{1} from the MDS repository

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-22010: SharedLibraryDeploymentCoordinator not found

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-22011: {0} is not a directory

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-22012: Failed to delete {0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-22013: {0} does not exist, so nothing to delete.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22014: Shared library {0}/{1} has subscribers.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-22015: The shared library {0}/{1} cannot be undeployed because it is referenced by one or more composites: {2}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-22016: A shared library classloader named {0} was created for {1}/{2}

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-22017: The classloader {0} for shared library {1}/{2} has been committed.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-22018: The following codesources were added to the shared library ({0}/{1}) classloader: {2}

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-22019: The classloader {0} for shared library {1}/{2} has been closed.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

SOA-22101: There was an error validating the composite patch on {1}: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-22102: There was an error validating composite patch(s) on {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-22103: The composite archive, {0}, does not contain a SAR file.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-22104: The SAR file, {0}, is not a composite patch archive.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-22105: The sar file, {0}, does not contain a SCA-INF/patch.xml file.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-22106: The deployed composite corresponding to the archive {0} cannot be found

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25000: set user and password...

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25001: set config plan...

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25002: sarLocation cannot be found: {0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25003: ---->Deploying composite success.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25004: ---->Response code={0}, error:{1}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25005: Exception:{0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25006: ---->Undeploying composite ({0}) success.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25007: Config plan was successfully attached.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25008: Must provide a sar file or composite.xml.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25009: Config plan file already exists, please provide overwrite as true to overwrite the file.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25010: Config plan was successfully generated.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25011: Config plan was successfully extracted.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25012: Config plan was successfully validated.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25013: Report file already exists, please provide overwrite as true to overwrite the file.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25014: Ant script does not exist: {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25015: oracle.home is not available. Please provide this property.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25016: Cannot find ANT script $oracle.home/bin/ant-sca-compile.xml.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25017: Invoking ANT script: {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25018: Cannot find ANT script $oracle.home/bin/ant-sca-package.xml.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25019: Cannot find ANT script $oracle.home/bin/ant-sca-test.xml.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25020: Cannot find composite lifecycle mbean.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25021: Composite ({0}) is successfully started.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25022: Composite ({0}) is successfully stopped.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25023: Composite ({0}) is successfully activated.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25024: Composite ({0}) is successfully retired.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25025: Composite ({0}) is successfully set as default composite.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25026: Invalid update type: {0}, please choose among: none/all/property/runtime.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25027: Removing existing sar file: {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25028: ---->Export composite success.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25029: Invalid update type: {0}, please choose among: all/property/runtime.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25030: Removing existing jar file: {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25031: ---->Export updates success.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25032: ---->Cannot find post deployment property updates.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25033: ---->Cannot find post deployment runtime/metadata updates.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25034: ---->Cannot find any post deployment updates.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25035: ---->Import updates success.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25036: ---->Export shared data success.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25037: ---->Cannot find shared data of given pattern: {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25038: Calling composite store mbean to export composite...

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25039: Composite was successfully exported.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25040: Calling composite store mbean to export composite with all post deployment updates ...

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25041: Composite with all post deployment updates was successfully exported.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25042: Calling composite store mbean to export composite with property post deployment updates ...

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25043: Composite with property post deployment updates was successfully exported.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25044: Calling composite store mbean to export composite with runtime post deployment updates ...

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25045: Composite with runtime post deployment updates was successfully exported.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25046: No connection to a server exists. This operation can be executed only in the online mode.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25047: INFO: SOA server down, use domain runtime mbean...

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25048: Cannot find composite store mbean on this server.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25049: Calling composite store mbean to export all post deployment updates, if any...

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25050: All post deployment updates of the composite was successfully exported.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25051: Calling composite store mbean to export property post deployment updates, if any...

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25052: Property post deployment updates of the composite was successfully exported.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25053: Calling composite store mbean to export runtime post deployment updates, if any...

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25054: Runtime post deployment updates of the composite was successfully exported.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25055: Calling composite store mbean to import post deployment updates...

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25056: Post deployment updates was successfully imported.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25057: Calling composite store mbean to export shared data...

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25058: Shared data was successfully exported.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25059: ---->Remove shared data success.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25060: SOA Folder was successfully created.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25061: Cannot find folder lifecycle mbean on this server.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25062: SOA Folder was successfully deleted.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25063: All composites in the folder were successfully started.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25064: All composites in the folder were successfully stopped.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25065: All composites in the folder were successfully activated.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25066: All composites in the folder were successfully retired.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25067: Cannot find jar file: {0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25068: Merge completed successfully, created merged updates in jar file: {0}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25069: Merge completed but no jar file created, check log file for details: {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

SOA-25070: Found multiple composite store mbeans.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25071: Found multiple domain runtime composite store mbeans.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25072: Cannot find composite store mbean on this server.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25073: start composite operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25074: Found multiple composite lifecycle mbeans.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25075: Cannot find composite lifecycle mbean on this server.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25076: stop composite operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25077: activate composite operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25078: retire composite operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25079: assign default composite operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25080: get default composite revision operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25081: list deployed composites operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25082: list composites in SOA folder operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25083: create folder operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25084: Found multiple folder mbeans.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25085: delete folder operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25086: start composites in folder operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25087: stop composites in folder operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25088: activate composites in folder operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25089: retire composites in folder operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25090: list all folder operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25091: Found multiple EDNConfig mbeans.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25092: Cannot find EDNConfig mbean on this server.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25093: EDN event delivery is successfully enabled.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25094: enable EDN events operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25095: EDN event delivery is successfully disabled.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25096: disable EDN events operation failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25097: SOA Platform is running and accepting requests.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25098: SOA Platform is not ready.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-25103: Composite ({0}) endpoint ({1}) is successfully activated.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25104: Composite ({0}) endpoint ({1}) is successfully deactivated.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25105: Requested updates cannot be found.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25106: Requested shared data cannot be found.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25107: SOA Platform is quiesced.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25108: SOA Platform is not quiesced.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Other

SOA-50000: This profile contains the standard SOA platform and the BPM technologies.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50001: This profile contains the SOA Foundation technologies.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50002: This profile contains the BPEL SOA components.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50003: This profile contains the BPEL and Workflow technologies.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50004: This profile contains the standard SOA platform and the BPM technologies, plus the FULL adapter set.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50005: This profile contains the SOA Foundation technologies, plus the FULL adapter Set.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50006: This profile contains the SOA Foundation technologies as well as the B2B technologies.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50007: This profile contains the standalone B2B/Healthcare technologies.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50008: This profile contains the SOA platform and BPM technologies enabled in version 11g. This profile is meant for upgrade use cases.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50009: This profile contains the SOA platform technologies enabled in version 11g. This profile is meant for upgrade use cases.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50010: Error occurred while trying to get the current SOA Profile name.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Deployment

SOA-50011: Error occurred while trying to obtain profile description for profile {0}.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Deployment

SOA-50012: Error occurred while trying to query the status of the SOA Technology {0}.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Deployment

SOA-50013: Error occurred while trying to change the current profile to {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50014: Error occurred while trying to get the domain directory from JRF.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50015: Error occurred while trying to get the domain install templates from CIE.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50016: Errors occurred while trying to obtain the list of supported profiles for this SOA domain. This likely means that there is a configuration error with the domain.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50017: No Profile found with this name {0}. Please select from one of the supported profiles.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50018: Exception occurred while trying to change profiles to {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50019: Error while attempting to get admin server connection info.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50020: Error occurred while creating WebLogic deployment Manager.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50021: No profile commands registered with this manager. This is likely a problem with the initialization of the profile manager.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50022: Attempt to change the current SOA Profile has failed. Please check the server log for details.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50023: Error occurred while trying to update the current SOA Profile to {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50024: Attempt to deploy internal modules failed during a targeting change for application {0}. Please check the server log for details.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50025: Attempt to undeploy internal modules failed during a targeting change for application {0}. Please check the server log for details.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50026: Error during edit session operation. The operation that failed is {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50027: Error occurred while trying to obtain the AppDeploymentMBean for application {0}. The MBean is not available.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50028: Error occurred while trying to obtain the source path for application {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50029: Error occurred while waiting for a deployment operation to complete. Deployment command is null.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50030: Error while trying to setup internal modules. Application {0} not available.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50031: Error in internal module setup for application {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50032: Error in internal module operation {0}. Deployment result is {1}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50033: No Targets were found that support soa-infra. This is a deployment error or an installation problem.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50034: Start module attempt for module name {0} failed. Deployment status = {1}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50035: Set of {0} modules for the new profile cannot be null.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50036: Set of {0} modules for the new profile cannot be empty.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50037: Exception encountered during {0} module targeting for SOA profile transition.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50038: Module name {0} to be targeted is not found. This could be an installation problem, or could mean that a profile was chosen that does not match with the components installed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50039: Module name {0} to be un-targeted is not found. This could be an installation problem, or could mean that a profile was chosen that does not match with the components installed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50040: Error occurred during targeting operations for a SOA Profile transition.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-50041: The Modularity operation for the following modules: ({0}) has timed out waiting for a server deployment operation to complete. Please increase the value of the {1} system property and restart the server before attempting this command again.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Deployment

SOA-65001: No global transaction is currently associated with the executing thread "{0}".

Cause: No global transaction is currently associated with the calling thread.

Action: Contact oracle support.

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65002: Failure to unwrap the wrapped DMS ExecutionContext "{0}" and associate it with the thread "{1}".

Cause: An error occured while unwrapping a DMS ExecutionContext.

Action: Contact oracle support.

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65003: An error occurred while executing SOA's Instance Tracking Audit interceptor. See nested exception for root cause.

Cause: An error occured while executing the SOA Instance Tracking Audit Interceptor.

Action: Correct issue associated with the error's route cause.

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65004: No FlowId is associated with request.

Cause: A request was not associated with a FlowId

Action: Contact oracle support.

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65005: No Component Instance ID is associated with the Executing Thread's DMS Execution Context

Cause: The Component Instance ID was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support.

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65006: No Component Instance ID creation time is associated with the Executing Thread's DMS Execution Context

Cause: The Component Instance ID creation time was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support.

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65007: The CommonFault associated with FaultId "{0}" could not be retrieved from the database.

Cause: The CommonFault associated with a given FaultId could not be retrieved

Action: Contact oracle support.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65008: The fault Id was not associated with the Executing Thread DMS Execution Context.

Cause: The fault Id was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65009: The fault context was not associated with the Executing Thread DMS Execution Context.

Cause: The fault context was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65010: The Composite Sca Entity ID was not associated with the Executing Thread DMS Execution Context.

Cause: The composite Sca Entity Id was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65011: No Object found with JNDI Name "{0}"

Cause: No Object found with this JNDI Name

Action: Check values provided

Level: 1

Type: ERROR

Impact: Configuration

SOA-65012: Cannot cast object with jndi name "{0}" to class "{1}"

Cause: Invalid Class assignment for object with this JNDI Name

Action: Contact oracle support

Level: 1

Type: ERROR

Impact: Configuration

SOA-65013: Invalid async component state process count with original value "{0}" to new value "{1}"

Cause: Invalid async parallel process count with conflict of original and new value

Action: Contact oracle support

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65014: Invalid async parallel process call sequence, the setPartialExecutions should be executed first with flow id "{0}" to component instance id "{1}"

Cause: Invalid async parallel process call sequence, the setPartialExecutions should be executed first.

Action: Contact oracle support

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65015: Invalid async component completed process count with new value "{0}" to available partial parallel process count value "{1}"

Cause: Invalid async completed process count with conflict of new value and available partial parallel process count value

Action: Contact oracle support

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65016: The FlowId "{0}" is not a valid FlowId. Valid values are numeric values.

Cause: Invalid FlowId format

Action: Contact oracle support.

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65017: The original Flow Event associated with the business flow "{0}" is missing.

Cause: Flow Trace issue.

Action: Contact oracle support.

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65018: Invalid SCAEntityId "{0}".

Cause: The SCAEntityId value is not valid.

Action: Contact oracle support.

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65019: The CommonFault associated with the Component Fault Key "{0}" could not be retrieved from the database.

Cause: No Fault is associated with the provided component fault key

Action: Contact oracle support.

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65020: The Composite Sca Entity ID Entry Time was not associated with the Executing Thread DMS Execution Context for the following FlowId "{0}".

Cause: The composite Sca Entity Id Entry Time was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65021: An error occurred while collecting sensor data.

Cause: An error occured while collecting sensor data

Action: Contact oracle support

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65022: An invalid Flow id value was provided "{0}".

Cause: An invalid FlowId value was provided.

Action: FlowId values must be positive numeric values.

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65023: Composite instance associated with FlowId "{0}" and Composite Instance Id "{1}" could not be found.

Cause: Internal instance tracking properties are missing.

Action: Contact oracle support

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65024: The JPA persistence layer is not in health state.

Cause: The JPA persistence layer is not in health state.

Action: Contact oracle support.

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65025: Unknown instance tracking policy name "{0}"

Cause: The supplied or configured instance tracking persistence policy name is unrecognized

Action: Configure the policy with a valid policy name choice

Level: 1

Type: WARNING

Impact: Configuration

SOA-65026: Setting instance tracking persistence policy to "{0}"

Cause: The instance tracking policy has been initialized on server start or reconfigured

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-65027: Unknown audit store policy name "{0}"

Cause: The supplied or configured audit store policy name is unrecognized

Action: Configure the policy with a valid policy name choice

Level: 1

Type: WARNING

Impact: Configuration

SOA-65028: Setting audit store policy to "{0}"

Cause: The audit store policy has been initialized on first use after server start

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-65029: Changing the audit store policy from "{1}" to "{0}"

Cause: The audit store policy has been reconfigured by the administrative user

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-65030: ''undeploy'' event was received for composite "{0}" and ScaEntityId "{1}". Marking associated active composite instances as stale.

Cause: Marking composite instance as stale suring undeployment

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-65031: The following error occurred while marking composite instances as stale during undeployment for composite "{0}" and ScaEntityId "{1}". {2}

Cause: An error occured while marking composite instances as stale during undeployment

Action:

Level: 1

Type: ERROR

Impact: Configuration

SOA-65032: The callback properties associated with Flow Id "{0}", Component Instance Id "{1}" and Internal Id "{2}" could not be retrieved.

Cause: Callback properties could not be retrieved. See error message and associated Exception for details.

Action:

Level: 1

Type: WARNING

Impact: Configuration

SOA-65033: Invalid component instance id "{0}" associated with Flow Entry for Flow Id "{1}" and component type "{2}".

Cause: The provided component instance id could not be converted to a number.

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65034: Error while retrieving Composite Instance associated with Flow Id "{0}", Composite SCA Entity Id "{1}" and creation time "{2}".

Cause: See child exception.

Action: See child exception.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65035: Error while retrieving Flow events for correlated flow "{0}" from Flow "{1}".

Cause: See child exception.

Action: See child exception.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65036: The flow instance for Flow Id "{0}" could not be retrieved from the database

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65037: Error while retrieving Flow events for correlated flow "{0}" associated with Correlation Flow ID "{1}".

Cause: See child exception.

Action: See child exception.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65038: null

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65039: null

Cause: See child exception.

Action: See child exception.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65040: Error while retrieving Composite Instance associated Composite Id "{0}".

Cause: See child exception.

Action: See child exception.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65041: AuditService is not available

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65042: An error occurred while creating DAO "{0}".

Cause: See child exception.

Action: See child exception.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65043: The Composite Instance ID was not associated with the Executing Thread DMS Execution Context for the following FlowId "{0}".

Cause: The composite instance ID was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65044: Error while retrieving Async Component State associated with Flow Id "{0}" and Component Instance Id "{1}".

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65045: The SCASensorValue associated with ComponentInstanceId "{0}" and SensorName "{1}" could not be retrieved from the database.

Cause: The SCASensorValue associated with the given ComponentInstanceId and SensorName could not be retrieved

Action: Contact oracle support.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65046: The SCAAsyncComponentState associated with FlowId "{0}" and ComponentInstanceId "{1}" could not be retrieved from the database.

Cause: The SCAAsyncComponentState associated with the given FlowId and ComponentInstanceId could not be retrieved

Action: Contact oracle support.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65047: The FlowInstance associated with FlowId "{0}" could not be retrieved from the database.

Cause: The FlowInstance associated with the given FlowId could not be retrieved

Action: Contact oracle support.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65048: The FlowInstance associated with CorrelationFlowId "{0}" could not be retrieved from the database.

Cause: The FlowInstance associated with the given CorrelationFlowId could not be retrieved

Action: Contact oracle support.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65049: An error occurred while retrieving DAO "{0}".

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65050: The FlowAssociation associated with FlowId "{0}" and CorrelationFlowId "{1}" could not be retrieved from the database.

Cause: The FlowAssociation associated with the given FlowId and CorrelationFlowId could not be retrieved

Action: Contact oracle support.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65051: The SCAMetaData associated with FlowId "{0}", CIKey "{1}", InternalID "{2}" and MetaDataCategory "{3}" could not be retrieved from the database.

Cause: The SCAMetaData associated with the given FlowId, CIKey, InternalId and MetaDataCategory could not be retrieved

Action: Contact oracle support.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65052: An error occurred while processing Flow Events associated with flow ID "{0}" in the context of migration.

Cause: Error while processing Flow Events associated with migration

Action: Contact oracle support.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65053: Cannot create audit store policy of type "{0}".

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65054: Cannot update null DAO.

Cause: The data access object was null

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65055: Failed to publish AuditEvent.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65056: Unknown audit store policy "{0}". Defaulting to policy "{1}".

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65057: Failed to retrieve SOA configuration while retrieving audit store policy. Defaulting to policy "{0}".

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65058: Policy "{0}" does not implement instance access policy.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65059: Failed to publish AuditDetails.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65060: Cannot flush buffered instances because there is no MGIContext currently set.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65061: Cannot participate in global transaction when MGIContext is using a local transaction.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65062: Cannot call onCommit before preCommit.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65063: Error performing operation "{0}".

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65064: Unsupported DAO type "{0}".

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65065: Failed to look up Spring bean "{0}"

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-65066: The callback properties associated with Flow Id "{0}", Component Instance Id "{1}" and Internal Id "{2}" could not be persisted.

Cause: Callback properties could not be persisted. See error message and associated Exception for details.

Action:

Level: 1

Type: WARNING

Impact: Configuration

SOA-65067: MGIContext is not set on current thread

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65068: Current thread is already associated with an MGIContext belonging to another FlowId. Existing MGIContext FlowId = {0}. Current FlowId = {1}.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65069: Exception while persisting Instance Tracking data as part of transaction rollback. Pending operations: "{0}". Transaction status: "{1}".

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65070: Exception while executing transaction synchronizer afterCompletion on TransactionSynchronizer "{0}"

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65071: Audit event:"{0}" is not persisted

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65072: The callback properties associated with Flow Id "{0}", Component Instance Id "{1}" and Internal Id "{2}" could not be found.

Cause: Either: 1) A write failure occurred while storing the callback properties during the original request 2) The original request used the local callback optimization but the callback did not use the optimization 3) The front end host configuration is misconfigured which can result in local optimization issues

Action: Either: 1) Check the logs for the host that made the request for any possible failures while persisting the callback properties 2) Check the composite.xml of this composite and ensure the "oracle.webservices.local.optimization" property is applied consistently to the participating bindings 3) Check the front end host configuration for the servers or cluster involved

Level: 1

Type: WARNING

Impact: Configuration

SOA-65073: The provided flow instance title "{0}" is longer than the allowable maximum of 100 characters. The operation will proceed but the title will be truncated to 100 characters.

Cause: The provided flow instance title is longer than the allowable maximum of 100 characters.

Action: No action required. The operation will proceed but the title will be truncated to 100 characters.

Level: 1

Type: WARNING

Impact: Configuration

SOA-65074: The provided composite instance title "{0}" is longer than the allowable maximum of 100 characters. The operation will proceed but the title will be truncated to 100 characters.

Cause: The provided composite instance title is longer than the allowable maximum of 100 characters.

Action: No action required. The operation will proceed but the title will be truncated to 100 characters.

Level: 1

Type: WARNING

Impact: Configuration

SOA-65075: An error occurred while converting the metrics to XML.

Cause: See nested exception.

Action: See nested exception.

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65076: Failure during ICS tracking integration

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-65077: Correlation Flow Id "{0}" of new MGIContext "{1}" does not match Correlation Flow Id "{2}" of existing MGIContext "{3}".

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-67001: CircuitBreaker: Fault occured for reference -> "{0}"

Cause: Downstream system is unavailable.

Action:

Level: 1

Type: TRACE

Impact: Programmatic

SOA-67002: CircuitBreaker: Resuming suspended service -> "{0}"

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67003: CircuitBreaker: Error sending notification when suspending/resuming a service

Cause: Error sending notification when suspending/resuming a service

Action:

Level: 1

Type: WARNING

Impact: Programmatic

SOA-67004: CircuitBreakerHistory: Adminstrator resumed {0} -> "{1}"

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67005: CircuitBreakerHistory: CircuitBreakerHistory: Resumed {0} -> "{1}" because downstream system is now available -> "{2}"

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67006: CircuitBreaker: Suspending service -> "{0}"

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-67007: The adapter has been suspended due to outbound endpoint errored {0} times in {1} minutes. Outbound Endpoint: {2} Composite: {3} Partition: {4} Suspended Since: {5} The suspended adapter will retry the flow every {6} minute(s) or you can resume the adapter manually from EM. SOA Infra -> {7}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-67008: CircuitBreakerHistory: Suspending {0} -> "{1}" because downstream system is unavailable -> "{2}"

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67009: CircuitBreaker: Schedule TrickleFeed for -> "{0}"

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67010: CircuitBreaker: Cancel TrickleFeed for -> "{0}"

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67011: CircuitBreaker: Initializing suspended services during initialization.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67012: CircuitBreaker: Suspending service -> "{0}"

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67013: CircuitBreaker: Trickle message for -> "{0}"

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67014: CircuitBreaker: Can't send trickle feed, ResiliencyManager not initialized in Fabric

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67015: CircuitBreakerHistory: CircuitBreakerHistory: Resumed Web Service -> "{0}"

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-67016: CircuitBreaker: Removing suspended services for undployed composite -> "{0}"

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67017: CircuitBreaker: Resuming service -> "{0}"

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-67018: "{0}" has been resumed because the outbound endpoint, "{1}" has recovered.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-67019: "{0}" has been manually resumed by the administrator

Cause:

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-67020: ResiliencyPersistenceStore: Error while binding the Spring Application Context associate with SOA Resiliency Persistence functionality

Cause: Error while binding the Spring Application Context associate with SOA Resiliency Persistence functionality

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-67021: ResiliencyPersistenceStore: Error looking up EntityManager using JDNI name "{0}" for persistence unit 'soa_resiliency_persistence_unit'.

Cause: Error looking up EntityManager for persistence unit 'soa_resiliency_persistence_unit'.

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-67022: CircuitBreaker: Schedule Ramp-up job for -> "{0}" ({1}ms over {2} minutes)

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67023: CircuitBreaker: Cancel Ramp-up job for -> "{0}"

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67024: CircuitBreaker: Set process delay of "{0}" for -> "{1}"

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67025: CircuitBreaker: Can't update process delay, ResiliencyManager not initialized in Fabric

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67026: CircuitBreaker: Adapter type "{0}" does not support suspend/resume functionality

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67027: CircuitBreaker: Error looking up the RestService, "{0}", using RestServiceStore

Cause: Error looking up a RestService using RestServiceStore

Action:

Level: 1

Type: ERROR

Impact: Programmatic

SOA-67028: CircuitBreaker: Error reading/writing to resiliency tables

Cause: Error reading or writting to resiliency tables.

Action:

Level: 1

Type: ERROR

Impact: Programmatic