43 OSB-75050 to OSB-2032402

OSB-75050: Missing parameter: parentClassLoader

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.

Level: 1

Type: ERROR

Impact: Other

OSB-75051: Missing parameter: mwHome

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.

Level: 1

Type: ERROR

Impact: Other

OSB-75052: Missing parameter: mbeanServerType

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.

Level: 1

Type: ERROR

Impact: Other

OSB-75053: Missing parameter: username

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.

Level: 1

Type: ERROR

Impact: Other

OSB-75054: Missing parameter: password

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.

Level: 1

Type: ERROR

Impact: Other

OSB-75055: Missing parameter: inputName

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.

Level: 1

Type: ERROR

Impact: Other

OSB-75056: Missing parameter: address

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.

Level: 1

Type: ERROR

Impact: Other

OSB-75057: Missing parameter: protocol

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.

Level: 1

Type: ERROR

Impact: Other

OSB-75058: Missing parameter: port

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.

Level: 1

Type: ERROR

Impact: Other

OSB-75059: No channel supporting a JMX protocol found in appliance

Cause: Unable to find a suitable channel supporting a JMX protocol.

Action: Ensure that the appliance is configured with a suitable channel.

Level: 1

Type: ERROR

Impact: Other

OSB-75060: MBeanServerConnection already closed

Cause: Something has already closed the MBeanServerConnection. This should not happen.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-75061: Importing of some (or all) OSB resources failed

Cause: Importing of some (or all) OSB resources failed. The log file should contain more detail.

Action: Check the log file for more details and correct the errors.

Level: 1

Type: ERROR

Impact: Other

OSB-75062: Importing the configuration plan failed: {0}

Cause: Importing the configuration plan failed. The error message will provide more details.

Action: Correct the error described.

Level: 1

Type: ERROR

Impact: Other

OSB-380000: General runtime error: {0}

Cause: A generic runtime error has occured in OSB transport subsystem while processing the message. There should be a specific message that describes specific cause of the problem. This error typically occurs when an exception is thrown during the outbound call, but it can also be explicitly raised by the outbound transport implementation, in which case, it may have a customized the message associated with it.

Action: If this is an unexpected error happening on a customized transport, check for unchecked exceptions in outbound call implementation. For other transports, check the documentation corresponding to this error code. Contact Oracle Support Services when this is an OSB runtime internal error.

Level: 1

Type: ERROR

Impact: Other

OSB-380001: Application error: {0}

Cause: An application error has occured in OSB transport subsystem while processing the message. There should be a specific message that describes specific cause of the problem. Only transports that explicitly declare support for application errors can return such errors. This error is explicitly raised by the transport implementation and usually has a customized message associated with it. It is used by OSB to prevent unnecessary retries.

Action: Check in the transport documentation describing application errors.

Level: 1

Type: ERROR

Impact: Other

OSB-380002: Connection error: {0}

Cause: A connection error has occured in OSB transport subsystem while processing the message. There should be a specific message that describes specific cause of the problem. This error is raised by the transport implementation and usually has a customized message associated with it. It is used by OSB to put a URI offline.

Action: Check in the transport documentation describing connection errors.

Level: 1

Type: ERROR

Impact: Other

OSB-380003: Exception on {0}, {1}

Cause: An unexpected runtime error has occured in OSB transport subsystem while processing the message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-380004: Version mismatch for service {0}

Cause: The processing of the response message has failed in OSB transport subsystem due to the fact that the configuration for the business service is in flux. This service is unable to send an outbound message until the configuration stabilizes.

Action: Wait until the configuration of OSB server stabilizes and retry sending the request.

Level: 1

Type: ERROR

Impact: Configuration

OSB-380006: No transport provider registered with ID: {0}

Cause: There is no transport provider deployed on the OSB server for the specified ID

Action: Verify that the transport provider application for that specified ID was correctly deployed on the OSB server. If this happens during server start up, it is also possible that the transport is registered too late. If so, try lowering its deployment order.

Level: 1

Type: ERROR

Impact: Deployment

OSB-380008: Provider with ID {0} does not support proxy service endpoints

Cause: The transport provider configuration does not support inbound endpoints, but somehow the configuration framework tried to create or update an inbound endpoint for that provider

Action: If this is a custom provider, verify that transport provider XML configuration is consistent with the generated endpoint configuration. Otherwise, contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-380009: Provider with ID {0} does not support business service endpoints

Cause: The transport provider configuration does not support outbound endpoints, but somehow the configuration framework tried to create or update an outbound endpoint for that provider

Action: If this is a custom provider, verify that the transport provider XML configuration is consistent with the generated endpoint configuration. Otherwise, contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-380010: Invalid endpoint configuration: provider specific configuration is missing

Cause: The provider for that endpoint declares a provider specific XML Schema Type but the endpoint configuration contains no provider specific configuration

Action: If this is a custom provider, verify that the provider specific definition is correctly set in the implementation. Otherwise, contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Deployment

OSB-380011: Invalid endpoint configuration: provider specific configuration is not valid

Cause: The endpoint configuration contains a provider specific configuration but the provider for that endpoint does not declare any provider specific XML Schema Type

Action: If this is a custom provider, check that its implementation returns the appropriate schema type corresponding to the provider specific configuration. Otherwise, contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-380012: Proxy Service configuration requires exactly one URI

Cause: Proxy Service configuration requires exactly one URI

Action: If this is a custom provider, verify the proxy service configuration is correctly initialized. Otherwise, contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-380013: Business Service configuration requires at least one URI

Cause: Business Service configuration requires at least one URI

Action: If this is a custom provider, verify the business service configuration is correctly initialized. Otherwise, contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-380014: Invalid endpoint configuration: Provider with ID {0} does not declare application errors

Cause: The endpoint supports application errors but the provider for that endpoint does not

Action: If this is a custom provider, verify that transport provider XML configuration is consistent with the generated endpoint configuration. Otherwise, contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-380015: Business Service do not support duplicate URIs. Service {0} found with duplicate URI {1}.

Cause: This error happens during configuration update: the URI of one of the updated Business Service is already used

Action: Delete Business Service or use a different URI

Level: 1

Type: ERROR

Impact: Configuration

OSB-380016: None of the URIs are online for Business service {0}

Cause: The Business service is configured to put URIs offline upon connection errors and there is no online URIs left to route messages sent to this service

Action: Check the service configuration and the server connections

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-380017: Transport configuration xml file is invalid: {0} : {1}

Cause: The transport provider configuration xml file is either syntactically or semantically incorrect. The message body should include the error description and the invalid XML snippet

Action: Correct the configuration

Level: 1

Type: ERROR

Impact: Configuration

OSB-380018: Configured service type is not supported by the transport ({0}).

Cause: The configured service type is not supported by the transport ({0}).

Action: If you are trying to import a config jar, your service definition is corrupted, or the current OSB version no longer support the binding defined in the config jar, re-create the service with the new supported binding. For any other reasons, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Data

OSB-380019: Service transport configuration is in flux: ({0}).

Cause: The service transport configuration is in flux: ({0}).

Action: If you modified your service transport configuration, messages received after the change is committed will be processed normally. For any other reasons, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Configuration

OSB-380020: Service ({0}) has been disabled.

Cause: The service ({0}) has been disabled.

Action: Enable the service, messages received after the change is committed will be processed normally. For any other reasons, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Configuration

OSB-380103: An unexpected throttling error occurred while processing message sent to business service {0}: {1}

Cause: An internal error occurred in the throttling sub-system. The message body should include the throttled service on which the error occurred and the message describing the problem: this error can be due to a transactional error, interrupted thread exception, timeout or an invalid runtime state

Action: If this is due to an invalid runtime state, contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-380500: Exception in {0}, {1}

Cause: An unexpected exception has occurred in OSB Transport subsystem. There should be an error message that points to cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-380501: Target not found: {0}

Cause: An unexpected error has occured while deploying or un-deploying a WLS artifact for the specified service. The deployment target {0} is not in the known list of available targets for OSB domain.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Deployment

OSB-381001: Error encountered while creating the endpoint {0}: {1}

Cause: An unexpected exception occurred in OSB Email transport while creating the endpoint. There should be an error message that points to the cause of the problem.

Action: Check that the endpoint configuration is formed properly.

Level: 1

Type: ERROR

Impact: Deployment

OSB-381002: Unable to find file path {0} for the service endpoint {1}. Current Process may not have access to this file or the file doesn't exist: {2}

Cause: Unable to find the intermediary file path while processing the message. This error may not be fatal and can appear even if the message is successfully processed once. This typically happens if the server is restarted while processing Email transport messages.

Action: Make sure that current user has read, write permission for the given file path location.

Level: 1

Type: ERROR

Impact: Files

OSB-381003: Initialization Error.

Cause: An unexpected exception occured while initializing the Email Transport Provider.

Action: Contact technical support.

Level: 1

Type: ERROR

Impact: Deployment

OSB-381004: Error while parsing or reading the service configuration.

Cause: Service configuration may have been corrupted.

Action: Check that the endpoint configuration is formed properly.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381005: Could not create or find the file with the path {0} while saving email attachments at location {1}

Cause: File could not be created at this location. current user may not have read, write permission at the given file path location.

Action: Make sure that current user has read, write permission for the given file path location. Please check that file location is valid.

Level: 1

Type: ERROR

Impact: Files

OSB-381006: Error encountered while saving the Email attachments for the email Part with file name {0} at location {1}: {2}

Cause: Email attachments could not be saved due to an unexpected error. There should be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.

Level: 1

Type: ERROR

Impact: Files

OSB-381007: In address {0}, the port is not a number.

Cause: Port is not a positive integer.

Action: Make sure that port is an integer greater than 0.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381008: Error encountered while creating Internet email address from address, personal name and header encoding as {0}, {1} and {2} respectively: {3}

Cause: An unexpected exception has occurred in Email service endpoint while creating the address. There should be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381009: Error encountered while creating Internet email address from address and header encoding as {0} and {1} respectively: {2}

Cause: An unexpected exception has occurred in Email service endpoint while creating the address. There should be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381010: Could not connect to remote Email server {0} for the service endpoint {1}

Cause: Email proxy service could not connect to the remote email server. Server address may be incorrect or server may be down currently.

Action: Make sure that the service endpoint URI points to the correct Email server address.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381011: Error occured for the service endpoint {0}: {1}

Cause: An unexpected general purpose exception has occurred in OSB Email transport. There should be an error message that points to cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381012: Could not delete temporary file {0} for Email Proxy Service: {1}

Cause: File could not be deleted from this location. Current user may not have read, write permission at the given file path location.

Action: Make sure that current user has read, write permission for the given file path location. Please check that file location is valid.

Level: 1

Type: ERROR

Impact: Files

OSB-381013: Error encountered while processing the Inbox messages for Email Proxy Service {0}: {1}

Cause: Error encountered while processing the message after the pipeline is invoked. Post processing may involve moving the message to a different folder or archiving the file.

Action: There should be an error message that points to the cause of the problem.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381014: URI {0} for this proxy service is already used by another proxy service: {1} with same service account.

Cause: An error had occured while registering a new Email proxy service: The URI configured for this proxy service is already used by another Email proxy service. Each Email proxy service has to have a unique URI if the service account is same.

Action: Check the transport configuration for Email proxy service and make sure that combination of URI and the service account is unique.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381015: Error while parsing or reading the Email Endpoint configuration.

Cause: Endpoint configuration may have been corrupted..

Action: Check that the endpoint configuration is formed properly.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381016: Exception cause {0}: {1}

Cause: An unexpected exception occured.

Action: Contact Oracle Support Services. There should be an error message that points to the cause of the problem.

Level: 1

Type: ERROR

Impact: Other

OSB-381017: Invalid pass by reference is set, it can only be true when the message type is of type XML.

Cause: Pass by reference is configured with non-xml message type Email proxy service.

Action: If Pass by reference is true, Email proxy service should be configured with xml message types.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381018: Given service account {0} is not of static type. Only static service accounts are supported with Email proxy and business services.

Cause: Service account is not of static type.

Action: Make sure that the service account configured in Email proxy or business service is a static service account.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381019: Service account does not exist.

Cause: Service account does not exist.

Action: Make sure that service account with the configured name exists in the OSB project.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381020: Exception encountered while upgrade. There should be an error message that points to the cause of the problem.

Cause: There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Deployment

OSB-381021: Invalid read limit {0}, it should be greater than or equal to zero.

Cause: Read limit is the number of email messages polled by the Email proxy service in a polling cycle. It should always be greater than or equal to zero.

Action: Make sure that read limit is greater than or equal to zero.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381022: Invalid polling interval {0}, it should be greater than zero.

Cause: Email Server is polled for new email messages by the Email proxy service after every poll interval. It should be greater than zero.

Action: Make sure that the polling interval is greater than zero.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381023: Invalid mail protocol {0}

Cause: Mail protocols supported by Email proxy service are POP3 and IMAP.

Action: Make sure that mail protocol is either POP3 or IMAP.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381024: Folder name is missing for the service configured with IMAP and post read action as Move.

Cause: Folder name is missing for the service configured with IMAP and post read action as Move.

Action: Make sure that folder name is specified in case Email proxy service is configured with IMAP transfer protocol and the post read action as Move.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381025: Download directory is missing.

Cause: Download directory is a required configuration parameter. Email messages are first staged in the download directory before invoking the pipeline.

Action: Make sure that download directory is specified.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381026: Error directory is missing.

Cause: Error directory is a required configuration parameter. Email messages are moved to this directory in case of processing errors.

Action: Make sure that error directory is specified.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381027: Archive directory is missing.

Cause: Archive directory is required in case pass by reference or pass attachments by reference is true.

Action: Make sure that archive directory is specified.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381028: Invalid PostRead option: {0}

Cause: Invalid post read option.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-381029: Given encoding is invalid: {0}

Cause: Encoding name is incorrect or the particular encoding is not supported by the Java virtual machine.

Action: Make sure that the Email proxy service is configured with supported encoding.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381030: Neither SMTP resource nor mail session configured.

Cause: Either SMTP resource or mail session should be configured for the Email business service. It must be provided either in transport configuration or as the uri parameter.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-381031: Connection timeout can not be negative: {0}.

Cause: Connection timeout is negative.

Action: Make sure that connection timeout is greater than or equal to zero.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381032: Reply to address can not be empty if reply to name is specified.

Cause: Reply to address is empty though reply to name is specified.

Action: Make sure that both Reply To Name and Reply to Address fields are defined.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381033: From address can not be empty if from name is specified.

Cause: From address is empty though from name is specified.

Action: Make sure that both From Address and From Name fields are defined.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381034: URI {0} is not valid.

Cause: URI is not formed properly.

Action: Make sure that the URI follows the correct syntax.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381035: Mail session with the jndi name {0} does not exist in the weblogic server instance.

Cause: Service should be configured with the mail session which exists in the weblogic server instance.

Action: Make sure that the mail session exists in the weblogic server instance.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381036: SMTP Ref {0} does not exist.

Cause: SMTP Ref mentioned in URI does exist in OSB

Action: Create the mentioned SMTP ref in OSB

Level: 1

Type: ERROR

Impact: Configuration

OSB-381037: Both Mail session and SMTP server cannot be configured

Cause: Either mail session or smtp server may be configured.

Action: Remove either or mail session or smtp server from the configuration

Level: 1

Type: ERROR

Impact: Configuration

OSB-381038: Invalid parameter in uri : {0}

Cause: Invalid parameter in the URI. Only mail session and SMTP are valid parameters.

Action: Provide the correct parameter in the uri.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381039: Error while initializing the SSL : {0}

Cause: Error while initializing the SSL

Action: There should be an error message that points to the cause of the problem.

Level: 1

Type: ERROR

Impact: Security

OSB-381040: Destination URI does not exist in resource {0}

Cause: Destination URI does not exist.

Action: Destination URI does not exist in the target resource.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381041: Socket I/O timeout can not be negative: {0}.

Cause: Socket I/O timeout is negative.

Action: Make sure that Socket I/O timeout is greater than or equal to zero.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381042: Email Server connection failed with SSL enabled : {0} Trying to connect using TLS

Cause: Either Email Server doesn't support SSL or it may down

Action: Make sure that Email Server Support SSL and it is running

Level: 1

Type: ERROR

Impact: Security

OSB-381043: Failed to establish a TLS Connection : {0} This may be because of trust certificate was not found. Please refer to the documentation for a list of valid locations to store the trust certification

Cause: Either Email Server doesn't support TLS or it may down

Action: Make sure that Email Server Support TLS and it is running

Level: 1

Type: ERROR

Impact: Security

OSB-381101: Error encountered while creating the endpoint {0}: {1}

Cause: An unexpected exception has occurred in OSB FTP transport while creating the endpoint. There should be an error message that points to the cause of the problem.

Action: Check that the endpoint configuration is formed properly.

Level: 1

Type: ERROR

Impact: Deployment

OSB-381102: Service Account Reference is missing in the FTP service configuration.

Cause: Service Account Reference is missing in the FTP service configuration.

Action: Make sure that service account is specified in the FTP service configuration.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381103: Invalid polling interval {0}, it should be greater than zero.

Cause: FTP Server is polled for new files by the Ftp proxy service after every poll interval. It should be greater than zero.

Action: Make sure that the polling interval is greater than zero.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381104: Error while parsing or reading the Ftp Endpoint configuration.

Cause: Error while parsing or reading the Ftp Endpoint configuration.

Action: Check that the endpoint configuration is formed properly.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381105: Error occured for the service endpoint: {0}

Cause: An unexpected general purpose exception has occurred in OSB Ftp transport. There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-381106: Unable to get file {0} on attempt number {1}: {2}

Cause: Could not retrieve the file.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Files

OSB-381107: Credential not found for alias {0}: {1}

Cause: Credentials could not be retrieved.

Action: Make sure that the credentials with the given name exists in the OSB domain.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381109: File: {0} was read from the remote FTP server: {1} but could not be deleted after processing.

Cause: File read through FTP proxy service could not be deleted. Current user may not have read, write permission.

Action: Make sure that Ftp proxy service has exclusive access to the remote file. Also the current user should have read, write permission.

Level: 1

Type: ERROR

Impact: Files

OSB-381111: URI Syntax error for the path {0}: {1}

Cause: URI is not formed properly.

Action: Make sure that the URI follows the correct syntax.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381112: Unable to rename file {1} on the remote host {0} for the service endpoint {2}

Cause: Remote FTP file could not be renamed. Current user may not have read, write permission.

Action: Make sure that Ftp proxy service has exclusive access to the remote file. Also the current user should have read, write permission.

Level: 1

Type: ERROR

Impact: Files

OSB-381114: File {1} could not be renamed to {2} on the remote host {0} for the service endpoint {3}: {4}

Cause: Exception encountered while executing renaming the file on the remote FTP server.

Action: Make sure that Ftp proxy service has exclusive access to the remote file. Also the current user should have read, write permission.

Level: 1

Type: ERROR

Impact: Files

OSB-381115: File {1} could not be deleted on the remote host {0} for the Ftp proxy service {2}

Cause: Exception encountered while deleting the file on the remote FTP server.

Action: Make sure that Ftp proxy service has exclusive access to the remote file. Also the current user should have read, write permission.

Level: 1

Type: ERROR

Impact: Files

OSB-381116: URI {0} for this proxy service is already used by another proxy service: {1} with same file mask.

Cause: An error had occured while registering a new Ftp proxy service: The URI configured for this proxy service is already used by another Ftp proxy service. Each Ftp proxy service has to have a unique URI if the file mask is same.

Action: Check the transport configuration for Ftp proxy service and make sure that the combination of URI and the file mask is unique.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381117: Exception in {0}: {1}

Cause: Exception encountered while executing this method. There should be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.

Level: 1

Type: ERROR

Impact: Other

OSB-381118: Invalid pass by reference is set, it can only be true when the message type is of type XML.

Cause: Pass by reference is configured with non-xml message type Ftp proxy service.

Action: If Pass by reference is true, Ftp proxy service should be configured with xml message types.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381119: Given service account {0} is not of static type. Only static service accounts are supported with FTP proxy and business services.

Cause: Configured service account is not of static type.

Action: Make sure that the service account configured in FTP proxy or business service is a static service account.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381120: Service account {0} does not exist.

Cause: Configured service account does not exist.

Action: Make sure that service account with the configured name exists in the OSB project.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381121: Given encoding {0} is invalid

Cause: Encoding name is incorrect or the particular encoding is not supported by the Java virtual machine.

Action: Make sure that the Ftp proxy service is configured with supported encoding.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381122: Retry count {0} should be greater than zero.

Cause: At the time of polling the FTP server for new files, FTP connection failures are tried for the number of times as specified by retry Count. It should be greater than zero.

Action: Make sure that retry count is greater than zero.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381123: Invalid socket timeout {0}, it should be greater than or equal to zero.

Cause: Configured socket timeout is invalid.

Action: Make sure that socket timeout is greater than or equal to zero.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381124: Invalid read limit {0}, it should be greater than or equal to zero.

Cause: Read limit is the number of message polled by the Ftp proxy service in a polling cycle. It should always be greater than or equal to zero.

Action: Make sure that read limit is greater than or equal to zero.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381125: Archive directory should be specified in case Ftp proxy service is configured with Pass by Reference as true.

Cause: Archive directory is not configured for pass by reference as true.

Action: Make sure that archive directory points to valid file path.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381126: Invalid transfer mode, it should be either binary or ascii.

Cause: Invalid transfer mode.

Action: Make sure that transfer encoding is either binary or ascii.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381150: Directory: {0} creation failed for the endpoint: {1}

Cause: Directory required to generate the ejb endpoints files could not be created.

Action: Check that the OSB process has the permission to create the directory.

Level: 1

Type: ERROR

Impact: Files

OSB-381151: Endpoint {0} could not be initialized: {1}

Cause: Endpoint could not be initialized.

Action: Exception message may point to the cause of the issue.

Level: 1

Type: ERROR

Impact: Deployment

OSB-381152: WSDL generation failed for the Endpoint {0} with exception: {1}

Cause: WSDL generation failed.

Action: Exception message may point to the cause of the issue.

Level: 1

Type: ERROR

Impact: Deployment

OSB-381153: JWS generation failed for the Endpoint {0} with error message(s): {1}

Cause: JWS generation failed.

Action: Error message(s) may point to the cause of the error.

Level: 1

Type: ERROR

Impact: Deployment

OSB-381201: Error encountered while creating the endpoint {0}: {1}

Cause: An unexpected exception has occurred in OSB File transport while creating the endpoint. There should be an error message that points to the cause of the problem.

Action: Check that the endpoint configuration is formed properly.

Level: 1

Type: ERROR

Impact: Deployment

OSB-381202: Could not create the directory: {0}

Cause: Directory with the given path could not be created. Directory path may be incorrect or the current user may not have the permission to create the files at this location.

Action: Make sure that the directory path is correct and the user has permissions to create the files at this location.

Level: 1

Type: ERROR

Impact: Files

OSB-381203: Invalid pass by reference is set, it can only be true when the message type is of XML.

Cause: Pass by reference is configured with non-xml message type File proxy service.

Action: If Pass by reference is true, File proxy service should be configured with xml message types.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381204: Exception in {0}: {1}

Cause: Exception encountered while executing this method. There should be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.

Level: 1

Type: ERROR

Impact: Other

OSB-381205: Error occured for endpoint {0}: {1}

Cause: An unexpected general purpose exception has occurred in OSB File transport. There should be an error message that points to cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381206: URI {0} is not valid.

Cause: URI is not formed properly.

Action: Make sure that the URI follows the correct syntax.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381207: Error occured while performing file operations: {0}

Cause: Message could not be written to the File Business service outbound directory. Current user may not have read, write permission for this location.

Action: Make sure that current user has read, write permission for the given directory path location.

Level: 1

Type: ERROR

Impact: Files

OSB-381208: Error occured while processing inbound file for File Proxy Service {0}: {1}

Cause: File could not be processed due to an unexpected error. There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-381209: Poller target server should be specified in case of cluster domain.

Cause: Poller target server should be specified in case of cluster domain.

Action: Make sure that the File proxy configuration has one of the managed servers as poller target server if it is running in the cluster.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381210: File cannot be moved from location {0} to the stage directory. Current Process may not have permission to do this operation.

Cause: Current user may not have read, write permission for the given file path location.

Action: Make sure that current user has read, write permission for the given file path location.

Level: 1

Type: ERROR

Impact: Files

OSB-381211: Unable to find file path: {0}. Current Process may not have access to this file or the file doesn't exist.

Cause: Unable to find the intermediary file path while processing the message. This error may not be fatal and can appear even if the message is successfully processed once. This typically happens if the server is restarted at the time it is processing some File transport messages.

Action: Make sure that current user has read, write permission for the given file path location.

Level: 1

Type: ERROR

Impact: Files

OSB-381212: URI {0} for this proxy service is already used by another proxy service: {1} with same file mask.

Cause: An error had occured while registering a new File proxy service: The URI configured for this proxy service is already used by another File proxy service. Each File proxy service has to have a unique URI.

Action: Check the transport configuration for File proxy service and make sure that unique value for the URI is used.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381213: Could not parse this endpoint configuration.

Cause: Could not parse the endpoint configuration.

Action: Check that the endpoint configuration is formed properly.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-381214: Endpoint-uri and archive directory path can not be the same.

Cause: Endpoint-uri and archive directory path can not be the same.

Action: Make sure that endpoint-uri and archive directory point to the different locations.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381215: Error occured while moving the file to the location {0}: {1}

Cause: File proxy service could not move the file to this location. Current user may not have read, write permission for this location.

Action: Make sure that current user has read, write permission for the given file path location.

Level: 1

Type: ERROR

Impact: Files

OSB-381216: Directory {0} could not be created.

Cause: Directory could not be created with this file path. Current user may not have read, write permission for this location.

Action: Make sure that current user has read, write permission for the given directory path location.

Level: 1

Type: ERROR

Impact: Files

OSB-381217: Error encountered while setting the max read limit size through system property: {0}

Cause: Error encountered while setting the max read limit size through system property. Max read limit size in an integer.

Action: Make sure that the max read limit is an integer.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381218: Directory Couldn't created for the Service Reference: {0}

Cause: Error encountered while creating directory.

Action: Make sure that that permission enabled for directory creation.

Level: 1

Type: ERROR

Impact: Files

OSB-381250: Unexpected error happened in the Transport at {0} due to {1}

Cause: An internal error occurred.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381251: URI "{0}" is not valid for this endpoint.

Cause: The SOA-DIRECT business service is called with URI "{0}". The URI is either empty, or does not conform to the URI format for the SOA-DIRECT transport.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-381252: The callback marker URI is not a valid URI.

Cause: The SOA-DIRECT business service is invoked with the callback marker URI, which is not a valid URI at runtime.

Action: there are different ways the URI was set as the callback marker URI: - dynamically overridden in the pipeline - the business service is configured with the marker URI and the pipeline logic did not override it Check the pipeline and/or SOAP headers and make sure the correct URI is configured.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381253: An unexpected error occurred while reading either the MessageID and/or RelatesTo headers: {0}

Cause: An unexpected error occurred while reading either the MessageID and/or RelatesTo headers. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381254: An unexpected error occurred while setting/updating the ReplyTo address: {0}

Cause: An unexpected error occurred while setting/updating the ReplyTo address. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381255: An error occurred while un-marshalling the request message: {0}

Cause: An error occurred while un-marshalling the request message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381256: An error occurred while transforming the payload: {0}

Cause: The Oracle SOA suite is based on the DOM object model. An error occurred while transforming the payload message into a DOM object. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381257: An unexpected error occurred initialization DOM support for the transport: {0}

Cause: There may be a server configuration problem preventing correct initialization of the DOM factory. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-381258: Operation "{0}" is not valid for this endpoint.

Cause: The SOA-DIRECT business service is called with operation "{0}". The operation is either empty, or not defined for the configured WSDL binding.

Action: Check the configuration of the pipeline to make sure the operation is set and configured with a valid value.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381259: Could not invoke proxy service {0} due to {1}

Cause: An Remote Exception happened while trying to invoke the SOA-DIRECT Transport proxy service via RMI

Action: Check your that network connection, destination server and port are up. Also, check that the remote proxy service still exists

Level: 1

Type: ERROR

Impact: Other

OSB-381260: An error occurred while marshalling the response message: {0}

Cause: An error occurred while marshalling the response message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381261: An error occurred while marshalling the Business fault: {0}

Cause: An error occurred while marshalling the Business fault. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381262: An unexpected error occurred while setting/updating the FaultTo address: {0}

Cause: An unexpected error occurred while setting/updating the FaultTo address. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381263: An unexpected error occurred while checking whether a transaction is running: {0}

Cause: An unexpected error occurred while checking whether a transaction is running. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381264: No callback address for WSA ReplyTo or FaultTo header

Cause: There is no callback address for the WSA callback header: neither the endpoint defines a physical address nor the header defines a callback address.

Action: Set a physical callback address in the transport configuration for this header, or manually add it in the pipeline

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381304: Exception in {0}: {1}

Cause: An unexpected exception has occurred in OSB HTTP transport. There should be an error message that points to cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381316: X.509 token identity assertion is not enabled in the security realm

Cause: An identity asserter with X.509 token support enabled is required because HTTPS inbound endpoint {0} specifies CLIENT-CERT authentication

Action: Enable X.509 identity assertion in your Identity Assertion provider in the security realm pages of the WebLogic Server console

Level: 1

Type: ERROR

Impact: Security

OSB-381317: The X.509 username-mapper sub-plugin of the default identity asserter in not configured

Cause: HTTPS inbound endpoint {0} specifies CLIENT-CERT authentication, therefore the username mapper properties of the default identity asserter must be configured (this is required to support 2-way SSL)

Action: Configure the username-mapper fields of the Default Identity Assertion provider in the security realm pages of the WebLogic Server console

Level: 1

Type: ERROR

Impact: Security

OSB-381318: URI {0} for this proxy service is already used by another proxy service: {1}

Cause: An error had occured while registering a new HTTP proxy service: The URI configured for this proxy service is already used by another HTTP proxy service or WS proxy service. Each HTTP proxy service has to have a unique URI.

Action: Check the transport configuration for HTTP proxy service and make sure that unique value for the URI is used.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381319: HTTP business service URLs must start with either http:// or https:// and have a hostname

Cause: An error had occured while registering a new HTTP business service: One of the URLs configured for the business service is invalid. According to RFC 2616, HTTP urls must start with http:// and have a hostname

Action: Check the transport configuration for HTTP business service and make sure that a valid URL is being entered

Level: 1

Type: ERROR

Impact: Configuration

OSB-381320: Cannot create an inbound HTTP endpoint with absolute URI {0}

Cause: An error had occured while registering a new HTTP proxy service: The URI configured for this proxy service is an absolute URI. Only relative URIs are supported for HTTP proxy services.

Action: Check the transport configuration for HTTP proxy service and make sure that only a relative URI (e.g. "/someName") is used.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381321: URI {0} for this proxy service is already used by OSB Kernel application

Cause: An error had occured while registering a new HTTP proxy service: The URI configured for this proxy service "/" is already used internal OSB Kernel application.

Action: Check the transport configuration for HTTP proxy service and make sure that a different unique value is used for the URI of this proxy

Level: 1

Type: ERROR

Impact: Configuration

OSB-381322: Failed to add a header named {0}: HTTP headers need to be string, instead {1} was found

Cause: There was a problem while setting specified header name/value pair in outbound HTTP request or inbound response. HTTP transport only allows String header values while another data type was given. One way it could happen is when using transport header action to pass all transport headers through from one transport that supports non-String headers, such as JMS, to HTTP transport

Action: Check the pipeline configuration to make sure only Strings are used to set transport header values of HTTP outbound request or inbound response

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381323: SSL client authentication is not allowed over plain-text HTTP

Cause: The proxy service is configured for client-certificate authentication but it is not an https endpoint. Client-certificate authentication is only allowed over https endpoints

Action: Set the https-required flag to true in the transport configuration page

Level: 1

Type: ERROR

Impact: Security

OSB-381324: Invalid http transport-level authentication configuration: custom token authentication is not supported on business services

Cause: The HTTP transport configuration of this outbound endpoint specifies custom-token authentication. This is not supported in this Oracle Service Bus release

Action: Change the authentication method in the endpoint configuration page

Level: 1

Type: ERROR

Impact: Security

OSB-381326: Invalid http transport-level custom token authentication configuration: header name has not been specified

Cause: Transport-level custom token authentication requires you to specify the name of the HTTP header that will carry the token

Action: Edit the http endpoint configuration details and specify the name of the custom token http header

Level: 1

Type: ERROR

Impact: Security

OSB-381327: Transport-level custom token identity assertion failed

Cause: Transport-level custom token identity assertion failed

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381328: Inbound http BASIC authentication failed

Cause: Inbound http BASIC authentication failed

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-381329: Inbound SSL client certificate authentication failed

Cause: Inbound SSL client certificate authentication failed

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-381330: Outbound HTTP request resulted in failure due to {0} : {1}. Request will be retried

Cause: HTTP request is failed with an application error.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381331: A token-type must be configured when using custom token authentication

Cause: The endpoint is configured for custom token authentication. A token-type must be specified

Action: In the HTTP transport-specific configuration page, choose a token-type from the drop-down list or select a different authentication method

Level: 1

Type: ERROR

Impact: Security

OSB-381332: The name of the HTTP header which carries the custom token must be specified

Cause: The endpoint is configured for custom token authentication. The name of the HTTP header which carries the custom token must be specified

Action: In the HTTP transport-specific configuration page, enter the name of the HTTP header or select a different authentication method

Level: 1

Type: ERROR

Impact: Security

OSB-381333: HTTP method "GET" is only allowed for Service Type any xml or messaging type with none as the request type.

Cause: "GET" method can not be configured for this service. It is allowed only for Service Type of any xml or messaging type with none as the request type.

Action: Check the transport configuration for HTTP business service and make sure that a valid HTTP method name is being entered.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381334: HTTP methods "PUT" and "DELETE" are only allowed for Service Type any xml or messaging type.

Cause: "PUT" and "DELETE" methods can not be configured for this service. It is allowed only for Service Type of any xml or messaging type

Action: Check the transport configuration for HTTP business service and make sure that a valid HTTP method name is being entered.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381335: HTTP method "HEAD" is only allowed for Service Type any xml or messaging type with none as the response type.

Cause: "HEAD" method can not be configured for this service. It is allowed only for Service Type of any xml or messaging type with none as the response type.

Action: Check the transport configuration for HTTP business service and make sure that a valid HTTP method name is being entered.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381336: HTTP business service has no URIs configured.

Cause: Business service is not configured with any URIs.

Action: Check the transport configuration for HTTP business service and make sure that URI set should not be empty.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381337: HTTP business service cannot have both ''chunked streaming mode'' and ''follow HTTP redirects'' options enabled.

Cause: HTTP business service cannot have both ''chunked streaming mode'' and ''follow HTTP redirects'' options enabled.

Action: Check the transport configuration for HTTP business service and make sure that both ''chunked streaming mode'' and ''follow HTTP redirects'' options are not enabled.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381338: Invalid http transport-level authentication configuration: custom authentication is not supported on proxy services

Cause: The HTTP transport configuration of this inbound endpoint specifies custom authentication. This is not supported in this Oracle Service Bus release

Action: Change the authentication method in the endpoint configuration page

Level: 1

Type: ERROR

Impact: Security

OSB-381339: Invalid http transport-level custom authentication configuration: custom authentication class name has not been specified

Cause: Transport-level custom authentication requires you to specify the name of the class that implements the custom authentication.

Action: Edit the http endpoint configuration details and specify the name of the custom authentication class.

Level: 1

Type: ERROR

Impact: Security

OSB-381341: Custom authentication class: "{0}" is not an implementation of "OutboundAuthentication" interface.

Cause: Transport-level custom authentication requires you to specify the name of the class that implements the com.bea.wli.sb.transports.http.OutboundAuthentication interface.

Action: Edit the http endpoint configuration details and specify the name of the class that implements the com.bea.wli.sb.transports.http.OutboundAuthentication interface.

Level: 1

Type: ERROR

Impact: Security

OSB-381342: Custom authentication class: "{0}" is not available in the system classpath.

Cause: Could not find custom authentication class in system classpath.

Action: Please make sure that the Custom authentication class: "{0}" is available as part of the system classpath.

Level: 1

Type: ERROR

Impact: Security

OSB-381343: Rejecting a non HTTP POST request due to WS-I compliance rules for service with context path {0} .

Cause: Non HTTP POST request is rejected due to WS-I compliance rules.

Action: Rejecting a non HTTP POST request due to WS-I compliance rules. User should send a POST request the service.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381401: Exception in {0}: {1}

Cause: An unexpected general purpose exception has occurred in OSB WS transport. There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-381404: One or more endpoint URLs in this WS transport business service are plain HTTP URLs but policy requires the HTTPS protocol

Cause: This endpoint's policy requires HTTPS access. All URLs in this endpoint must use the HTTPS protocol

Action: Edit the endpoint URLs to make sure all URLs use the HTTPS protocol

Level: 1

Type: ERROR

Impact: Configuration

OSB-381405: URI {0} for this proxy service is already used by OSB Kernel application

Cause: An error had occured while registering a new WS proxy service: The URI configured for this proxy service "/" is already used by internal OSB Kernel application.

Action: Check the transport configuration for WS proxy service and make sure that a different unique value is used for the URI of this proxy.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381406: Cannot create an inbound WS endpoint with absolute URI {0}

Cause: An error had occured while registering a new WS proxy service: The URI configured for this proxy service is an absolute URI. Only relative URIs are supported for WS proxy services.

Action: Check the transport configuration for WS proxy service and make sure that only a relative URI (e.g. "/foo") is used.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381407: URI {0} for this proxy service is already used by another proxy service: {1}

Cause: An error had occured while registering a new WS proxy service: The URI configured for this proxy service is already used by another WS proxy service or HTTP proxy service. Each WS proxy service has to have a unique URI.

Action: Check the transport configuration for WS proxy service and make sure that unique value for the URI is used.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381408: WS business service should always have absolute URI. Given URI is not absolute: {0}

Cause: WS business service should have absolute URIs.

Action: Change the WS business service configuration and make sure that all the URIs should be absolute.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381409: WS outbound services can only have http and https schemes. Given URI has invalid scheme:{0}

Cause: An error occurred while registering new WS business service: WS business services can only have http and https schemes.

Action: Change the scheme of the WS business service to http or https.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381410: The ws-policy of the WS business service requires HTTPS BASIC authentication but no service account has been configured

Cause: An HTTPS BASIC authentication policy requires the endpoint to send a username/password when connecting to the back-end service. A service account specifies how to get the username/password and allows the endpoint to get the username/password. This endpoint is configured for outbound HTTPS BASIC authentication but the service account reference is null.

Action: Configure a service account reference in the endpoint configuration page.

Level: 1

Type: ERROR

Impact: Security

OSB-381411: An entry with key:{0} is timed out in WsCorrelationTable.

Cause: While invoking a WS business service, a response to a WS request did not arrive in before the specified response timeout occurred.

Action: Check that WS business service or the target webservice is functioning properly and increase the response timeout value if necessary.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381412: An error occured while sending the message reliably to the target reliable webservice.

Cause: Reliable delivery failure has occurred while sending the message to the target reliable webservice. This failure might be because of Sequence timeout, inactivity timeout, authentication/authorization failures or bad certificate errors etc.

Action: Check that WS business service or the target webservice is functioning properly.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381413: URI:{0} of WS proxy service has '/' at the end.

Cause: WS proxy services should not have an ending '/' in URI.

Action: Remove the ending '/' in the URI of the WS proxy service.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381414: Attempting an indirect send to a WS transport proxy which requires BASIC authentication ({0}). Proxy-to-proxy routing and test console access are not allowed with this pattern

Cause: WS transport proxy services which require username/password (i.e. BASIC) authentication cannot be invoked from another proxy or from the test console.

Action: Check the message flow configuration and make sure there are no proxy-to-proxy routes where the target proxy service is a WS transport endpoint with BASIC authentication. Also, whenever using the test console to test such a WS transport proxy, make sure you set the "direct call" check-box to true.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381415: X.509 token identity assertion is not enabled in the security realm. An identity asserter with X.509 token support enabled is required because ws proxy service "{0}" has a ws-policy which requires CLIENT-CERT authentication

Cause: An identity asserter with X.509 token support enabled is required whenever the ws-policy requires CLIENT-CERT authentication

Action: Enable X.509 identity assertion in your Identity Assertion provider in the security realm pages of the WebLogic Server console

Level: 1

Type: ERROR

Impact: Security

OSB-381416: The X.509 username-mapper sub-plugin of the default identity asserter in not configured. The username-mapper is required because ws proxy service "{0}" has a ws-policy which requires CLIENT-CERT authentication

Cause: An identity asserter with X.509 token support enabled and username-mapper plugin enabled is required whenever the ws-policy requires CLIENT-CERT authentication (this is required to support 2-way SSL)

Action: Configure the username-mapper fields of the Default Identity Assertion provider in the security realm pages of the WebLogic Server console

Level: 1

Type: ERROR

Impact: Security

OSB-381417: WS transport proxy "{0}" is configured with client-certificate-required policy and is deployed in a cluster. There is typically a load-balancer between the client and the cluster. The load balancer forwards client-certificates to the server, but the server will only honor this certificate if it is configured with "Client Cert Proxy Enabled", otherwise the certificate will be ignored and the request will fail.

Cause: Typically, when a WS transport proxy is configured with client-certificate-required policy and is deployed in a cluster, the managed servers must be configured with "Client Cert Proxy Enabled". This is so that the managed servers will honor the certificate in the "WL-Proxy-Client-Cert" HTTP header. Make sure to read the section on SSL configuration in WebLogic Server documentation when using this feature.

Action: Set "Client Cert Proxy Enabled" to true in the WLS console. This can be done at the cluster level or individually for each managed server in the cluster. Make sure to read the section on SSL configuration in WebLogic Server documentation when using this feature. Use a weblogic.security.net.ConnectionFilter to ensure that this WebLogic Server instance accepts connections only from the machine on which the proxy-server plugin is running, otherwise you will create a security vulnerability because the WL-Proxy-Client-Cert header can be spoofed.

Level: 1

Type: ERROR

Impact: Security

OSB-381418: Unexpected failure while processing an incoming message for endpoint {0}

Cause: There was an unexpected error while processing an inbound message by specified WS proxy service.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-381419: WS business service URLs must start with either http:// or https:// and have a hostname

Cause: An error had occured while registering a new WS business service: One of the URLs configured for the business service is invalid. According to RFC 2616, HTTP urls must start with http:// and have a hostname.

Action: Check the transport configuration for WS business service and make sure that a valid URL is being entered.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381422: Sending the failed request message to error queue is failed for service: {0} with error : {1}

Cause: Error queue configured for the service may not be available or it may not be accepting the messages from OSB as the security credentials do not match.

Action: Make sure configured error queue is available and provide right credentials to the service.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381450: An unexpected error occured initialization DOM support for the transport: {0}

Cause: There may be a server configuration problem preventing correct initialization of the DOM factory. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Deployment

OSB-381451: An error occured while accessing the credentials for the JNDI connection: {0}

Cause: An error occured while accessing the credentials for the JNDI connection. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-381452: The Oracle BPEL delivery service could not be accessed: {0}

Cause: An error occured while doing the lookup of the delivery service to the Oracle BPEL Process Manager.

Action: Make sure the target Oracle BPEL Process Manager is running, that the host and port are correctly configured and that the business service has the correct credentials.

Level: 1

Type: ERROR

Impact: Process

OSB-381453: Operation "{0}" is not valid for this endpoint.

Cause: The BPEL business service is called with operation "{0}". The operation is either empty, or not defined for the configured WSDL binding.

Action: Check the configuration of the pipeline to make sure the operation is set and configured with a valid value.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381454: URI "{0}" is not valid for this endpoint.

Cause: The BPEL business service is called with URI "{0}". The URI is either empty, or does not conform to the URI format for the BPEL transport.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381455: The callback marker URI is not a valid URI.

Cause: The BPEL business service is invoked with the callback marker URI, which is not a valid URI at runtime.

Action: There are different ways the URI was set as the callback marker URI: - dynamically overridden in the pipeline - the business service is configured with the marker URI and the pipeline logic did not override it Check the pipeline and/or SOAP headers, and make sure the correct URI is configured.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381456: An error occured while transforming the payload: {0}

Cause: The Oracle BPEL PM is based on the DOM object model. An error occured while transforming the payload message into a DOM object. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381457: An error occured while un-marshalling the request message: {0}

Cause: An error occured while un-marshalling the request message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381458: An error occured while marshalling the response message: {0}

Cause: An error occured while marshalling the response message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381459: An error occured while marshalling the BPEL fault: {0}

Cause: An error occured while marshalling the BPEL fault. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381460: An unexpected error occured while setting/updating the ReplyTo address: {0}

Cause: An unexpected error occured while setting/updating the ReplyTo address. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381461: An unexpected error occured while reading either the MessageID and/or RelatesTo headers: {0}

Cause: An unexpected error occured while reading either the MessageID and/or RelatesTo headers. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381462: The protocol "{0}" does not support transaction propagation.

Cause: The protocol "{0}" does not support transaction propagation.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381463: An unexpected error occured while checking whether a transaction is running: {0}

Cause: An unexpected error occured while checking whether a transaction is running. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381464: An unexpected error occured trying to suspend the transaction: {0}

Cause: An unexpected error occured trying to suspend the transaction. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381465: An unexpected error occured trying to resume the transaction: {0}

Cause: An unexpected error occured trying to resume the transaction. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381502: Exception in {0}: {1}

Cause: An unexpected general purpose exception has occurred in OSB JMS transport. There should be an error message that points to cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381506: Unexpected type of message received: {0}

Cause: A non Text or Bytes or Object message was received by JMS proxy service or as a response to JMS business service. OSB JMS transport only supports Text, Bytes and Object messages.

Action: Make sure only JMS Text or Bytes messages are being sent to OSB JMS proxy or business services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381510: Error writing jar file: {0}

Cause: There was an unexpected error while generating JMS service-related artifacts. There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381511: Unexpected failure while processing an incoming message for endpoint {0}

Cause: There was an unexpected error while processing an inbound message by specified JMS proxy service. This may have happened due mis-configuration of the service

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381512: JMS Endpoint with name {0} already registered

Cause: There was an unexpected error at session activation time while registering a new JMS service. Two or more JMS services share the same name.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-381513: The URIs for request and response may not be equal

Cause: In the configuration for the JMS proxy service the request and response URIs are the same. Such configuration is not legal as it will most likely result in an infinite loop and request/response processing.

Action: Make sure that request and response URIs have different values in JMS proxy service configuration

Level: 1

Type: ERROR

Impact: Configuration

OSB-381514: Service binding(SOAP/XML/WSDL) has request/response operations but JMS transport configuration does not have any response information.

Cause: Service binding(SOAP/XML/WSDL) has request/response operations but JMS transport configuration does not have any response information.

Action: Make sure that the JMS transport configuration of the service is consistent with declared service binding type.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381515: Invalid target for JMS proxy: {0}

Cause: The target configured for JMS proxy service is not valid in the current cluster configuration. This may have happened if cluster configuration has recently changed or when this JMS service was moved (exported and imported) from one cluster to another.

Action: Make sure that the configured target (server or cluster) corresponds to one of the valid target names in the drop-down list of available targets in JMS transport configuration

Level: 1

Type: ERROR

Impact: Configuration

OSB-381517: URI {0} for this proxy service is already used by another proxy service: {1} with no message selector

Cause: Two or more JMS proxy services are using the same URI. The operation cannot be completed because only a single JMS proxy is allowed to receive messages from a given JMS destination.

Action: Make sure that the given JMS proxy is the only one that is configured with the URI in question.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381518: The generated MDB EAR file name {0} for service {1} is already used by another service. Please change the name this service to avoid a collision.

Cause: There was an unexpected error while OSB was generating JMS service-related artifacts.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-381519: Failure while processing an incoming message for endpoint {0} due to service configuration in flux

Cause: The processing of the message has failed in OSB runtime due to the fact that the configurations for the proxy service is in flux. This proxy is unable to process messages until the configuration stabilizes.

Action: Wait until the configuration of OSB server stabilizes and retry sending the request.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381520: Connection factory {0} does not exist!

Cause: OSB JMS transport failed to look up the configured JMS connection factory for the service with JMSMessageID response pattern in specified JNDI provider at service activation time

Action: Make sure that the JNDI provider referred to by the JMS service URL is up and running and can be properly accessed at service activation time. Also make sure that the JNDI name of the configured connection factory corresponds to an existing connection factory object in JNDI provider.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381521: The response destination is null or is not a queue

Cause: The JMS destination configured for response is not a queue. Only JMS queues are supported destinations for responses to JMS proxy services.

Action: Check that the JMS response URI configured in JMS proxy service refers to a JMS queue.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381522: The JMS URI {0} is not valid

Cause: One or more of the URIs configured for JMS service is not in the format expected by OSB. The expected format is jms://host:port[,host:port]*/MyFactory/MyQueue where - host is the name of the server that is the JNDI provider - port is the port of the server that is the JNDI provider - MyFactory is the JNDI name of the connection factory - MyQueue is the JNDI name of the JMS destination

Action: Make sure that the URI string conforms to the expected format

Level: 1

Type: ERROR

Impact: Configuration

OSB-381523: The server name {0} is not configured in the table of response JNDI destinations

Cause: There was one or more missing target that corresponds to a managed server that is part of OSB cluster domain in the map of destinations JMS service that uses JMSMessageID correlation pattern. Each managed server has to have a corresponding unique destination. This may have happened if cluster configuration has recently changed or when this JMS service was moved (exported and imported) from one cluster to another.

Action: Make sure that the configured target (server or cluster) corresponds to one of the valid target names in the drop-down list of available targets in JMS transport configuration

Level: 1

Type: ERROR

Impact: Configuration

OSB-381524: response destination for {0} not found in table of response JNDI destinations

Cause: There was one or more missing destination that corresponds to a managed server that is part of OSB cluster domain in the map of destinations JMS service that uses JMSMessageID correlation pattern. Each managed server has to have a corresponding unique destination. This may have happened if cluster configuration has recently changed or when this JMS service was moved (exported and imported) from one cluster to another.

Action: Make sure that the configured target (server or cluster) corresponds to one of the valid target names in the drop-down list of available targets in JMS transport configuration

Level: 1

Type: ERROR

Impact: Configuration

OSB-381525: Cannot re-use the same destination {0} for {1}; use unique response destination for each managed server

Cause: There were two or more identical destination names configured for two different managed servers for JMS service with JMSMessageID correlation pattern. Each managed server has to have a corresponding unique destination. This may have happened if cluster configuration has recently changed or when this JMS service was moved (exported and imported) from one cluster to another.

Action: Make sure that each managed server name corresponds to a unique JMS destination name in JMS transport configuration for the service

Level: 1

Type: ERROR

Impact: Configuration

OSB-381526: Response JNDI Names map not found for JMSMessageID response pattern

Cause: There was a problem with the configuration of JMS service with JMSMessageID correlation pattern. The configuration is missing a required element that specifies the map of destinations for a set of managed servers.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-381527: Service Account {0} is not static. Only static service accounts are supported with JMS proxies and business services.

Cause: The service account used in the configuration of JMS service is not a static account (i.e. either pass-through or mapped). Only static service accounts are supported with JMS proxies and business services

Action: Check that the type of the service account used in the configuration of the service and make sure only static accounts are used.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381528: Attempting an indirect send to a proxy using the JMSMessageID response pattern. Proxy-to-proxy routing not allowed with this pattern.

Cause: Sending an outbound message from a proxy that routs to a JMS proxy with JMSMessageID response pattern is not supported

Action: Check the message flow configuration for the proxy and make sure it does not route to a JMS proxy that uses JMSMessageID response pattern

Level: 1

Type: ERROR

Impact: Configuration

OSB-381529: Transaction associated with message id {0} has failed due to status: {1}

Cause: A transaction has failed while waiting for response for JMS request/response service. As a result, any related response message will be ignored.

Action: Examine the log files to determine that cause of the transaction failure and/or retry sending the request. If the problem persists, contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381530: Failed to lookup connection factory {0}

Cause: OSB JMS transport failed to look up the configured JMS connection factory in specified JNDI provider at service activation time

Action: Make sure that the JNDI provider referred to by the JMS service URL is up and running and can be properly accessed at service activation time. Also make sure that the JNDI name of the configured connection factory corresponds to an existing connection factory object in JNDI provider.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381531: Inbound response will not be sent due to inbound request transaction status: {0}

Cause: A response to JMS proxy service will not be sent due to the fact that the transaction associated with the inbound request has failed due to stated reason.

Action: Examine the log files to determine that cause of the transaction failure and/or retry sending the request. If the problem persists, contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381533: {0} already exists and is not a Queue

Cause: The destination specified in JMS Transport configuration already exists and is not a JMS Queue.

Action: Make sure the JMS transport configuration is consistent with the existing objects available from specified JNDI provider. That means if one configures a queue in JMS transport page and an object with the specified JNDI name exists, it is expected to be a Queue

Level: 1

Type: ERROR

Impact: Configuration

OSB-381534: {0} already exists and is not a Topic

Cause: The destination specified in JMS Transport configuration already exists and is not a JMS Topic.

Action: Make sure the JMS transport configuration is consistent with the existing objects available from specified JNDI provider. That means if one configures a topic in JMS transport page and an object with the specified JNDI name exists, it is expected to be a Topic

Level: 1

Type: ERROR

Impact: Configuration

OSB-381535: {0} already exists and is not a TopicConnectionFactory

Cause: The connection factory specified in JMS Transport configuration already exists and is not an instance of JMS TopicConnectionfactory. Since the configured destination type is a topic, one needs to provide an instance of valid TopicConnectionFactory in the configuration

Action: Make sure the JMS transport configuration is consistent with the existing objects available from specified JNDI provider. That means if one configures a topic in JMS transport page and an object with the specified JNDI name exists, it is expected to be a TopicConnectionFactory

Level: 1

Type: ERROR

Impact: Configuration

OSB-381536: {0} is not a proxy service"

Cause: An unexpected error has occured during UDDI export of JMS services. The JMS service being exported was expected to be a proxy and was not.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-381537: JMS provider-specific configuration was not specified

Cause: There was an unexpected error processing the message while parsing the JMS transport-specific configuration of the service endpoint

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-381538: Request metadata XML must be an instance of {0}

Cause: There was an unexpected error processing the message while processing request metadata for the inbound or outbound request.

Action: Check the pipeline actions in your message flow and make sure that you are setting the request metadata in way that is consistent with the transport specified for the service. One can use Log actions to examine the contents of any message context variable.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381539: Response metadata XML must be an instance of {0}

Cause: There was an unexpected error processing the message while processing response metadata for the inbound or outbound request.

Action: Check the pipeline actions in your message flow and make sure that you are setting the response metadata in way that is consistent with the transport specified for the service. One can use Log actions to examine the contents of any message context variable.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381546: Unexpected JMS Object type of message received for service other than messaging service with sub-type 'Java'

Cause: A JMS Object type of message was received by JMS proxy service or as a response to JMS business service for service other than messaging service with sub-type 'Java'. Messages should be of type Text or Bytes.

Action: Make sure only JMS Text or Bytes messages are being sent to OSB JMS proxy or business services for service other than messaging service with sub-type 'Java'.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381547: Unexpected type of message: {0} received for service configured as messaging service with sub-type 'Java'

Cause: A Text or Bytes message was received by JMS proxy service or as a response to JMS business service for service configured as messaging service with sub-type 'Java'. Messages should be of type Object.

Action: Make sure only JMS Object messages are being sent to OSB JMS proxy or business services for service configured as messaging service with sub-type 'Java'.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381548: Service binding with response type 'Java' configured with incompatible response message type in the JMS transport configuration

Cause: The configuration of the JMS service was not compatible with the declared service binding type. A messaging service with 'Java' response type should not have a response message type configured in the JMS transport configuration. In this case, Object type of messages are sent as the response.

Action: Make sure that the JMS transport configuration should not have a response message type configured in the JMS transport configuration.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381549: Service binding with request type 'Java' configured with incompatible message type in the JMS transport configuration

Cause: The configuration of the JMS service was not compatible with the declared service binding type. A messaging service with 'Java' request type should not have a message type configured in the JMS transport configuration. In this case, Object type of messages are sent by the business service.

Action: Make sure that the JMS transport configuration should not have a message type configured in the JMS transport configuration.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381550: Payload from the pipeline not received with one java object

Cause: A message with java object should contain one java object.

Action: Make sure that the message contains only one java object.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381551: Response message type is not configured in service binding but JMS transport has response configuration.

Cause: The configuration of the JMS service is not compatible with the declared service binding type. JMS transport should not have response configuration as the service messaging type does not have any response.

Action: Make sure that the JMS transport configuration of the service is consistent with declared service binding type.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381552: Response message type is configured in service binding but JMS transport does not have any response configuration.

Cause: The configuration of the JMS service is not compatible with the declared service binding type. JMS transport should have response configuration as the service messaging type has response.

Action: Make sure that the JMS transport configuration of the service is consistent with declared service binding type.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381553: An update to proxy service {0} failed while modifying its deployment ear file, {1}.

Cause: An update to the JMS proxy service failed while updating its deployment ear file. Either the old version of the ear file could not be deleted or renaming the new ear file failed.

Action: Make sure that the named ear file exists in the sbgen subdirectory of the domain. If not, the service should be deleted and re-added to force the generation of a new ear file.

Level: 1

Type: ERROR

Impact: Deployment

OSB-381558: Proxy-to-proxy routing not allowed with this configuration: JMSCorrelationID response pattern and JMS_NO_MDB_FOR_RESPONSE=true.

Cause: When JMS_NO_MDB_FOR_RESPONSE property is set to true for a JMS proxy service, a default MDB will not be generated on inbound response queue, therefore, no response message will be received.

Action: Check the message flow configuration for the proxy and make sure it does not route to a JMS proxy that uses JMSCorrelationID response pattern combined with JMS_NO_MDB_FOR_RESPONSE property set to true.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381601: Error encountered while putting the message in the queue for the service endpoint {0}: {1}

Cause: Message may not be processed as there was an unexpected error while putting the message in the task queue. There should be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381602: Error encountered while polling the resource for the service endpoint {0}: {1}

Cause: Unexpected exception happened at the time of polling the external resource. There should be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381603: Error occured while polling the resource for the service endpoint {0}. Polling will be stopped: {1}

Cause: An unexpected exception occured at the time of polling the external resource. There should be an error message that points to the cause of the problem. This is a fatal error and may stop the polling of external resource.

Action: Reactivate the service or restart the server.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381604: Error while initializing the Transport Provider {0}: {1}

Cause: An unexpected exception occured while initializing the Transport Provider. There may be an error message that points to the cause of the problem.

Action: There may be an error message that points to the cause of the problem.

Level: 1

Type: ERROR

Impact: Deployment

OSB-381606: Error encountered while executing the task from PolledMessageListener MDB.

Cause: An unexpected exception occured while passing the message to the pipeline. There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381607: Error encountered while parsing the transport provider configuration file {0}: {1}

Cause: Error encountered while parsing the transport provider configuration file

Action: Contact technical support.

Level: 1

Type: ERROR

Impact: Deployment

OSB-381611: Poller target server should be specified in case of cluster domain.

Cause: Poller target server should be specified in case of cluster domain.

Action: Make sure that the File proxy configuration has one of the managed servers as poller target server if it is running in the cluster.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381612: Poller target server should belong to one of the managed servers in the OSB cluster domain.

Cause: Poller target server should belong to one of the managed servers in the OSB cluster domain.

Action: Make sure that the File proxy configuration has one of the managed servers as poller target server if it is running in the cluster.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381613: Service endpoint {0} activation failed: {1}

Cause: Service endpoint could not be activated due to an unexpected exception. There may be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.

Level: 1

Type: ERROR

Impact: Deployment

OSB-381614: Service endpoint {0} could not be resumed: {1}

Cause: Service endpoint could not be resumed due to an unexpected exception. There may be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.

Level: 1

Type: ERROR

Impact: Deployment

OSB-381651: Exception in {0}, {1}

Cause: An unexpected general purpose exception has occurred in OSB local transport. There should be an error message that points to cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381652: Local Proxy Services cannot have URIs

Cause: An invalid configuration has been found for a local proxy service during new service registration due to the presence of URIs. Local proxy services cannot be associated with any URIs.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-381653: Only local proxy services are supported

Cause: An invalid configuration has been found for a local service during new service registration. Only proxy services are supported for local transport.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-381700: Exception in {0}, {1}

Cause: An incoming Tuxedo request encountered a problem. See the error accompanying this message for more details

Action: Consult the Weblogic Server log for more details on the problem and contact Customer Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381701: Request failed. {0}

Cause: The Tuxedo call failed. The Tuxedo invocation encountered an error. Please refer to the accompanying message for more details.

Action: Verify the WTC configuration, remote Tuxedo configuration or see the local and remote logs for possible system or application errors.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381750: Unexpected error happened in the SB Transport at {0} due to {1}

Cause: An internal error occurred. It is due to either an unrecoverable failure during a configuration update or a runtime error during message processing

Action: If this error happened during a configuration update, check that your SB transport services are not corrupted. In case of corrupted configuration, manually clean up the failed services or restart your server. For other errors, Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-381751: Could not create connection with proxy service {0} due to {1}

Cause: An error happened while trying to lookup the SB Transport proxy service RMI stubs

Action: Verify that your JNDI context host, port and credentials are correct. Also check that protocol used by the JNDI context is supported and enabled. For instance, IIOP/IIOPS protocols are not supported between WebLogic Server, and HTTP/HTTPS protocols requires HTTP tunneling.

Level: 1

Type: ERROR

Impact: Other

OSB-381752: Could not invoke proxy service {0} due to {1}

Cause: An Remote Exception happened while trying to invoke the SB Transport proxy service via RMI

Action: Check your that network connection, destination server and port are up. Also, check that the remote proxy service still exists

Level: 1

Type: ERROR

Impact: Other

OSB-381753: Could not generate plan {0} due to {1}

Cause: An internal error occurred while creating a proxy services with a custom dispatch policy. The deployment plan for this proxy artifact could not be created

Action: The message body should give you more details about the error. This could be caused by a I/O Exception or because the location of the deployment plan write-protected.

Level: 1

Type: ERROR

Impact: Other

OSB-381754: Unsupported payload type {0}

Cause: An internal error occurred during the message processing: the payload associated with the message is not supported by the SB Transport

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381755: Operation "{0}" is not valid for this endpoint.

Cause: The SB Proxy service is called with operation "{0}". The operation is either empty, or not defined for the configured WSDL binding.

Action: Check the client configuration to make sure the operation is set and configured with a valid value.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381756: An unexpected error occured initialization DOM support for the transport: {0}

Cause: There may be a server configuration problem preventing correct initialization of the DOM factory. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-381757: An error occured while marshalling the response message: {0}

Cause: An error occured while marshalling the response message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381758: An error occured while transforming the payload: {0}

Cause: The Oracle SOA suite is based on the DOM object model. An error occured while transforming the payload message into a DOM object. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381759: An error occured while un-marshalling the request message: {0}

Cause: An error occured while un-marshalling the request message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381801: Error occured for endpoint {0}

Cause: Error occured for endpoint. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381802: Could not read file : {0} for Endpoint {1}:

Cause: The given file is not available or does not have read permissions

Action: Please verify the location of the file and check the read permissions

Level: 1

Type: ERROR

Impact: Other

OSB-381803: Unable to get file : {0} on attempt number : {1} :

Cause: Either the remote file does not exist or does not have read permissions

Action: Please check that the remote file exist and have read permissions

Level: 1

Type: ERROR

Impact: Other

OSB-381804: Credential not found for alias :{0} :

Cause: In case of ServiceAccount this may happen if the ServiceAccount does exist or it does not have any username password. In case of ServiceKeyProvider this may happen if the service key provider does not exist or does not have a key-pair for SSL client authentication

Action: In case of ServiceAccount, please verify if the username-password exists. In case of ServiceKeyProvider, please verify if the Key-Pair exists.

Level: 1

Type: ERROR

Impact: Other

OSB-381805: File: {0} moved to error directory path: {1}

Cause: Due to the error file could not be transferred to the destination. File is finally moved to the error directory after the retries mentioned in the business service. This could happen if the destination is not reachable or if the destination directory does not have permission to write the file.

Action: Please verify if the destination is reachable and it has the permissions to write the file.

Level: 1

Type: ERROR

Impact: Other

OSB-381807: URI Syntax error for the path : {0}

Cause: URI Syntax error occured due to Invalid URI provided.

Action: Please verify the syntax of the URI

Level: 1

Type: ERROR

Impact: Other

OSB-381808: Unable to rename file : {1} on remote host : {0} for endpoint :{2}

Cause: Error occured during file rename. This may happen if the file is not accessible, destination does not exist or does not have permissions to the destination directory.

Action: Please verify if the file exists and is accessible. For the destination directory, verify if the destination directory exists and has write permission to the destination directory.

Level: 1

Type: ERROR

Impact: Other

OSB-381810: File : {1} could not be renamed to {2} on remote host : {0} for endpoint :{3}

Cause: Error occured while renaming the file on the remote Host. It may happen if the remote destination is not accessible or if it does not have permissions to write the file.

Action: Please verify if the remote directory exists and is accessible. Ensure that it has necessary write permissions to put a file.

Level: 1

Type: ERROR

Impact: Other

OSB-381811: File : {1} could not be deleted on remote host : {0} for endpoint :{2}

Cause: File could not be delete on the remote Host. It may happen if the user does not have necessary permissions to delete the file or if the file is not accessible.

Action: Please ensure that the file is accessible and user has necessary permissions to delete the file.

Level: 1

Type: ERROR

Impact: Other

OSB-381812: File : {0} was read from remote server :{1} but unable to delete

Cause: File was read but it could not be deleted. It may happen when the client does not have permissions to delete the file.

Action: Please verify if the client has permissions to delete the file.

Level: 1

Type: ERROR

Impact: Other

OSB-381813: Could not parse this endpoint configuration.

Cause: Endpoint configuration could not be parsed.

Action: Contact Oracle Support.

Level: 1

Type: ERROR

Impact: Other

OSB-381814: Pass by reference can be true only when the message is of type XML.

Cause: Pass by reference can be true only when the message is of type XML.

Action: Do not use pass by reference when the message is not XML type

Level: 1

Type: ERROR

Impact: Other

OSB-381815: URI {0} for this proxy service is already used by another proxy service: {1} with same file mask.

Cause: The same URI and file mask is already in use by some other service.

Action: Change the URI or the file mask of one of the service to avoid this conflict.

Level: 1

Type: ERROR

Impact: Other

OSB-381816: Invalid polling interval, it should be greater than zero:{0}.

Cause: Invalid polling interval, it should be greater than zero.

Action: Please provide a valid polling interval, greater than zero.

Level: 1

Type: ERROR

Impact: Other

OSB-381817: Retry count should be greater than zero:{0}

Cause: Invalid Retry count provided.

Action: Please provide a valid Retry count greater than zero.

Level: 1

Type: ERROR

Impact: Other

OSB-381818: Timeout should be greater than zero.:{0}

Cause: Invalid timeout provided.

Action: Please provide a valid timeout greater than zero.

Level: 1

Type: ERROR

Impact: Other

OSB-381819: Invalid read limit, it should be greater than or equal to zero:{0}

Cause: Invalid read limit provided

Action: Please provide a valid read limit greater than or equal to zero.

Level: 1

Type: ERROR

Impact: Other

OSB-381820: Archive dir is invalid:{0}

Cause: Invalid Archive directory location

Action: Please verify the archive directory location provided.

Level: 1

Type: ERROR

Impact: Other

OSB-381821: Given encoding is invalid:{0}

Cause: Invalid encoding is provided

Action: Please verify the encoding provided.

Level: 1

Type: ERROR

Impact: Other

OSB-381822: ServiceAccountRef does not exist.

Cause: ServiceAccountRef does not exist.

Action: Please verify the ServiceAccount provided.

Level: 1

Type: ERROR

Impact: Other

OSB-381823: Given Service-Account:{0} is not of static type. Only static service accounts are supported with SFTP proxy and business services.

Cause: The given Service Account is not valid, SFTP service only works with static Service Accounts.

Action: Please use a Static Service Account for SFTP service.

Level: 1

Type: ERROR

Impact: Other

OSB-381824: Service account "{0}" does not exist.

Cause: Service Account does not exist

Action: Please verify the Service Account used for the service

Level: 1

Type: ERROR

Impact: Other

OSB-381825: Exception {1}

Cause: Exception occured in transport

Action: Contact Oracle Support

Level: 1

Type: ERROR

Impact: Other

OSB-381826: Key Not Found for host {0}

Cause: Public key of the remote SFTP server is not found in known_hosts file.

Action: Please verify the Public key of SFTP server exists in known_hosts file in the desired format.

Level: 1

Type: ERROR

Impact: Other

OSB-381827: Key Mismatch for host {0}

Cause: Public key for the SFTP server present in the known_hosts file does not match with the key exchanged with the server. The mismatch may happen if the Public Key of the SFTP server is updated on the server but the known_hosts file contains the old key. It may also happen if the Public key is not present for the algorithm used.

Action: Please verify the Public Key of the SFTP server in the known_hosts file. Update the known_hosts with the latest Public Key of the server.

Level: 1

Type: ERROR

Impact: Other

OSB-381828: SFTPClientException occured, message is :: {0}

Cause: SFTPClientException occured. The exception message should provide more detail.

Action: No action required

Level: 1

Type: ERROR

Impact: Other

OSB-381831: Archive file {0} does not exist.

Cause: Archive file does not exist or is not accessible

Action: Please verify that the archive location exists and has read-write permissions.

Level: 1

Type: ERROR

Impact: Other

OSB-381832: Local file {0} does not exist.

Cause: Local file does not exist in the download directory or does not have read permissions

Action: Please verify the download directory location and check for read permissions

Level: 1

Type: ERROR

Impact: Other

OSB-381833: Error in renaming file {0} to {1}

Cause: Error is renaming file to destination directory

Action: Please verify that the destination directory is accessible

Level: 1

Type: ERROR

Impact: Other

OSB-381834: End point does not exists for service {0}

Cause: EndPoint does not exist for the given service.

Action: Contact Oracle support

Level: 1

Type: ERROR

Impact: Other

OSB-381835: Service Key Provider Ref does not exist

Cause: Service Key Provider Ref does not exist

Action: Contact Oracle support

Level: 1

Type: ERROR

Impact: Other

OSB-381836: Key Pair not found for ref : {0}

Cause: Key Pair not found for ref.

Action: Contact Oracle support

Level: 1

Type: ERROR

Impact: Other

OSB-381837: Hostname in known_hosts file is null or blank

Cause: Bad known_hosts file format

Action: Fix the hostname in known_hosts and check for any extra spaces

Level: 1

Type: ERROR

Impact: Other

OSB-381838: Algorithm specified in known_hosts is null or blank. It should be ssh-rsa or ssh-dss

Cause: Bad known_hosts file format

Action: Fix the algorithm name in known_hosts

Level: 1

Type: ERROR

Impact: Other

OSB-381839: Bad Algorithm name "{0}", it should be ssh-rsa or ssh-dss.

Cause: Bad known_hosts file format

Action: Specify the correct algorithm name in known_hosts

Level: 1

Type: ERROR

Impact: Other

OSB-381840: Public key specified in known_hosts is null or blank.

Cause: Bad known_hosts file format

Action: Specify the correct public key in known_hosts and check for any extra spaces

Level: 1

Type: ERROR

Impact: Other

OSB-381841: known_hosts file does not exist or it does not have read permissions.

Cause: Known_hosts file not accessible

Action: Create the known_hosts file and provide read permissions

Level: 1

Type: ERROR

Impact: Other

OSB-381842: Invalid key specified for Host "{0}", it is not a {1} key

Cause: Wrong algorithm name specified for the key in known_hosts

Action: Specify the correct algorithm name for the key in known_hosts

Level: 1

Type: ERROR

Impact: Other

OSB-381843: Bad known_hosts file, there should be no space in "HOST,IP"

Cause: Found space in "HOST,IP" in known_hosts file

Action: Remove any space in "HOST,IP" in known_hosts file

Level: 1

Type: ERROR

Impact: Other

OSB-381901: Exception in {0}, {1}

Cause: An unexpected general purpose exception has occurred in OSB MQ transport. There should be an error message that points to cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-381904: Unexpected type of message received: {0}

Cause: An unexpected message type received.

Action: Make sure only MQ Text or Bytes messages are being sent to OSB JMS proxy or business services.

Level: 1

Type: ERROR

Impact: Data

OSB-381905: The URIs for request and response may not be equal

Cause: In the configuration for the MQ proxy service the request and response URIs are the same. Such configuration is not legal as it will most likely result in an infinite loop and request/response processing.

Action: Make sure that request and response URIs have different values in MQ proxy service configuration

Level: 1

Type: ERROR

Impact: Configuration

OSB-381906: URI {0} for this proxy service is already used by another proxy service: {1}

Cause: Two or more MQ proxy services are using the same URI. The operation cannot be completed because only a single MQ proxy is allowed to receive messages from a given MQ destination.

Action: Make sure that the given MQ proxy is the only one that is configured with the URI in question.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381907: The URI {0} is not valid

Cause: One or more of the URIs configured for MQ service is not in the format expected by OSB. The expected format is mq://host:port?conn=MyOSBProject/MyMQConnectionResource

Action: Make sure that the URI string conforms to the expected format

Level: 1

Type: ERROR

Impact: Configuration

OSB-381908: Failed to lookup MQ Connection Resource {0}

Cause: Failure when trying to lookup MQ Connection Resource specified in the URI of the service. The MQ connection resource specified in the URI may not exist.

Action: Please ensure that the MQ connection resource specified in the URI exists.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381909: Service binding is incompatible with transport configuration (response message type)

Cause: The configuration of the MQ service was not compatible with the declared service binding type. For example, a messaging service with non-'None' response type has to have a response destination configured in MQ transport configuration.

Action: Make sure that the MQ transport configuration of the service is consistent with declared service binding type.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381911: Endpoint: {0} activation failed.

Cause: Service endpoint could not be activated due to an unexpected exception. There may be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381912: Endpoint: {0} could not be resumed.

Cause: Service endpoint could not be resumed due to an unexpected exception. There may be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381913: Error occured while polling the resource for Endpoint: {0}. Polling will be stopped.

Cause: A fatal error has occured when trying to poll the MQ queue specified in the URI of the service.

Action: The error message may point to the cause of the problem.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381915: Error occured while polling the resource for response; Endpoint: {0}. Polling will be stopped.

Cause: A fatal error has occured when trying to poll the MQ queue specified in the response URI of the service.

Action: The error message may point to the cause of the problem.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381916: Error occured when connecting to MQ: {0}

Cause: An error has occured when trying to connect to the MQ server; please check the MQ reason code associated with the error for more details

Action: Please check the MQ reason code associated with the error for more details

Level: 1

Type: ERROR

Impact: Configuration

OSB-381919: The MQ Connection Resource {0} in URI {1} does not exist

Cause: The MQ Connection Resource does not exist.

Action: Make sure that the MQ connection resource referenced in the URI exists.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381920: The Unrecognized Response URI should not be the same as Response URI for the service

Cause: In the configuration for the MQ business service the Unrecognized Response URI and Response URI are the same. Such configuration is not legal as it will most likely result in an infinite loop and request/response processing.

Action: Make sure that Unrecognized Response URI and Response URI have different values in MQ business service configuration

Level: 1

Type: ERROR

Impact: Configuration

OSB-381921: Error trying to access queue {0}

Cause: OSB could not connect to the configured queue on MQ Server.

Action: Please check if the queue exists on the configured MQ Server.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381922: Error trying to send message to {0}; queue {1} not available.

Cause: OSB could not send message because queue in not available.

Action: Please check if the queue exists on the configured MQ Server.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381940: Error occured when connecting to MQ: {0}

Cause: An error has occured when trying to connect to the MQ server; please check the MQ reason code associated with the error for more details

Action: Please check the MQ reason code associated with the error for more details

Level: 1

Type: ERROR

Impact: Configuration

OSB-381941: Error occured when connecting to MQ. Unable to obtain pooled connection, Resource {0}. Pool size may need to be increased

Cause: An error has occured when trying to connect to the MQ server. Pool size for mq connection pool may need to be increased.

Action: Pool size for mq connection pool may need to be increased.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381942: Error occured when connecting to MQ. Unable to obtain pooled connection, Resource {0}. {1}

Cause: An error has occured when trying to connect to the MQ server. Please check the MQ reason code associated with the error for more details

Action: Please check the MQ reason code associated with the error for more details

Level: 1

Type: ERROR

Impact: Configuration

OSB-381950: Unexpected error happened in the JCA Transport at {0} due to {1}

Cause: An internal error occurred. It is due to either an unrecoverable failure during a configuration update or a runtime error during message processing

Action: If this error happened during a configuration update, check that your JCA transport services are not corrupted. In case of corrupted configuration, manually clean up the failed services or restart your server. For other errors, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-381951: JCA inbound request only invocation failed, exception: {0}

Cause: An exception was thrown during JCA inbound request only invocation

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381952: JCA inbound request response invocation failed, exception: {0}

Cause: An exception was thrown during JCA inbound request only invocation

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381953: Failed to create JCABindingReference for wsdl: {0}, operation: {1}, exception: {2}

Cause: An exception was thrown when creating JCA outbound JCABindingReference

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Deployment

OSB-381954: Failed to close JCABindingReference for wsdl: {0}, operation: {2}, exception: {3}

Cause: An exception was thrown when closing JCA outbound JCABindingReference

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Session

OSB-381955: JCA outbound one way invocation failed for wsdl: {0}, operation: {1}, request msg: {2}, exception: {3}

Cause: An exception was thrown when invoking JCA outbound request only endpoint

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381956: JCA outbound request response invocation failed for wsdl: {0}, operation: {1}, request msg: {2}, exception: {3}

Cause: An exception was thrown when invoking JCA outbound request response endpoint

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381957: Failed to create JCABindingService for wsdl: {0}, operation: {1}, exception: {2}

Cause: An exception was thrown when creating JCABindingService

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Session

OSB-381958: Failed to close JCABindingService for wsdl: {0}, operation: {1}, exception: {2}

Cause: An exception was thrown when closing JCABindingService

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Session

OSB-381959: Failed to activate JCABindingService for wsdl: {0}, operation: {1}, exception: {2}

Cause: An exception was thrown when activating JCABindingService

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Session

OSB-381960: Failed to deactivate JCABindingService for wsdl: {0}, operation: {1}, exception: {2}

Cause: An exception was thrown when deactivating JCABindingService

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Session

OSB-381961: Failed to create JCABindingService for wsdl: {0}, exception: {1}

Cause: An exception was thrown when creating JCABindingInterface

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Session

OSB-381962: Failed to transform message to DOM, message source: {0}, exception: {1}

Cause: An exception was thrown when transforming message source to DOM object

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381963: JCA transport failed to resume existing transaction after received response to inbound request for endpoint: {0}, operation: {1}, exception: {2}

Cause: An exception was thrown when resuming existing transaction after received response to inbound request

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381964: JCA transport outbound message was sent without specifying an operation

Cause: JCA transport outbound received a send message request without operation name.

Action: Message should be routed to JCA transport outbound service operation or the inbound service operation should be passed through to outbound.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381965: JCA transport outbound message was sent with invalid URI for the endpoint

Cause: JCA transport outbound received a send message request with an endpoint URI that is not for the endpoint.

Action: If this error happened during a configuration update, check that your JCA transport services are not corrupted. In case of corrupted configuration, manually clean up the failed services or restart your server. For other errors, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381966: Failed to get subject from credential call-back when invoking JCA outbound service, exception: {0}

Cause: Failed to get subject from credential call-back when invoking outbound JCA business service.

Action: See exception for more detail.

Level: 1

Type: ERROR

Impact: Security

OSB-381967: Invoke JCA outbound service failed with application error, exception: {0}

Cause: Exception occurred during JCA outbound service invocation. See server log for more detail.

Action: See server log for more detail.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381968: An unexpected error occurred initialization DOM support for the transport: {0}

Cause: There may be a server configuration problem preventing correct initialization of the DOM factory. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381969: JCA transport outbound message was sent with no URI for the endpoint

Cause: JCA transport outbound received a send message request with no endpoint URI set for the endpoint.

Action: Endpoint URI has to be set in TransportOptions when invoking JCA transport business service endpoint.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381970: No service information is registered for: {0}

Cause: JCA transport failed to find the service information using the service ref.

Action: If this error happened during a configuration update, check that your JCA transport services are not corrupted. In case of corrupted configuration, manually clean up the failed services or restart your server. For other errors, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381971: Invoke JCA outbound service failed with connection error, exception: {0}

Cause: Exception occurred during JCA outbound service invocation. See server log for more detail.

Action: See server log for more detail.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381972: Failed to create inbound JCABindingService for wsdl: {0}, operation: {1}, exception: {2}

Cause: An exception was thrown when creating inbound JCABindingService

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Session

OSB-381973: Failed to restore the original endpoint while trying to compensate for endpoint update failure. Endpoint: {0}, exception: {1}

Cause: Failed to compensate for endpoint update failure, create and activate JCA endpoint failed while trying to restore the original endpoint

Action: See exception for more detail

Level: 1

Type: ERROR

Impact: Session

OSB-381974: Operation "{0}" is not valid for this endpoint.

Cause: The JCA service is called with operation "{0}". The operation is either empty, or not defined for the configured WSDL binding.

Action: Check the configuration of the pipeline to make sure the operation is set and configured with a valid value.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381975: An error occurred while transforming the payload: {0}

Cause: The Oracle JCA adapter is based on the DOM object model. An error occurred while transforming the payload message into a DOM object. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381976: An error occurred while un-marshalling the request message: {0}

Cause: An error occurred while un-marshalling the request message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381977: An error occurred while marshalling the response message: {0}

Cause: An error occurred while marshalling the response message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381978: An error occurred while marshalling the JCA exception: {0}

Cause: An error occurred while marshalling the JCA exception. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381979: An error occurred while validating JCA transport endpoint, exception: {0}

Cause: An error occurred while validating the JCA transport endpoint. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Session

OSB-381980: Invoke JCA outbound service failed with application error

Cause: Exception occurred during JCA outbound service invocation. See server log for more detail.

Action: See server log for more detail.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381981: Upgrade JCA WSDL: {0} failed with exception: {1}

Cause: Exception occurred during JCA WSDL upgrade. See server log for more detail.

Action: See server log for more detail.

Level: 1

Type: ERROR

Impact: Upgrade

OSB-381982: Upgrade JCA service: {0} failed with exception: {1}

Cause: Exception occurred during JCA service upgrade. See server log for more detail.

Action: See server log for more detail.

Level: 1

Type: ERROR

Impact: Upgrade

OSB-381983: Resolve toplink mapping file: {0} to InputStream failed with exception: {1}

Cause: Exception occurred while trying to resolve toplink mapping file to input stream. See server log for more detail.

Action: See server log for more detail.

Level: 1

Type: ERROR

Impact: Files

OSB-381984: OSB JCA transport does not support adapter type: {0}

Cause: OSB JCA transport does not support the adapter. Please see OSB JCA transport documentation for more detail.

Action: OSB JCA transport does not support the adapter. Please see OSB JCA transport documentation for more detail.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381985: Failed to load OSBSupportedAdapter.xml, exception: {0}

Cause: OSB JCATransport failed loading OSBSupportedAdapter.xml.

Action: Please make sure OSBSupportedAdapter.xml contains valid adapter types.

Level: 1

Type: ERROR

Impact: Configuration

OSB-381986: An error occurred while validating JCA transport endpoint. JNDI lookup with URL: {0} failed due to lack of permission. Add a static service account to JCA service to specify the credentials for authentication.

Cause: Lookup adapter connection factory JNDI: {0} failed due to lack of permission. The JNDI is protected.

Action: Add a static service account to JCA service to specify the credentials for authentication

Level: 1

Type: ERROR

Impact: Security

OSB-381987: An error occurred while validating JCA transport endpoint. JNDI lookup with URL: {0} failed. Missing JNDI configuration such as undeployed or incorrectly configured JCA Adapter RAR or connection factory.

Cause: Lookup adapter connection factory JNDI: {0} failed. Missing JNDI configuration such as undeployed or incorrectly configured JCA Adapter RAR or connection factory.

Action: Configure an adapter connection factory with JNDI: {0}

Level: 1

Type: ERROR

Impact: Configuration

OSB-381988: An error occurred while validating JCA transport endpoint properties, exception: {0}

Cause: An error occurred while validating the JCA transport endpoint properties. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-382000: General runtime error: {0}

Cause: A general runtime error has occurred in OSB pipeline runtime while processing the message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-382001: Context variable names must be non-null and have non-zero length

Cause: A runtime error has occurred in OSB pipeline runtime while processing the message. Message context variable names must be non-null and have non-zero length

Action: Check your pipeline configuration to make sure all variable names are properly configured and have non-zero length

Level: 1

Type: ERROR

Impact: Configuration

OSB-382002: Router runtime cache has not been initialized on this node!

Cause: An unexpected error has occurred in during the initialization of OSB pipeline runtime while processing the request message for specified proxy service.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382003: Unknown error while processing message for service {0}

Cause: An error has occurred in OSB pipeline runtime while processing the request message for specified proxy service. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382004: Failed to process request message for service {0}: {1}

Cause: An error has occurred in OSB pipeline runtime while processing the request message for specified proxy service. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382005: Failed to process response message for service {0}: {1}

Cause: An error has occurred in OSB pipeline runtime while processing the response message for specified proxy service. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382006: No object is registered for ref ''{0}''

Cause: An error has occurred in OSB pipeline runtime while processing the response message for specified proxy service due to an attempt to look up an object in Java object repository with the specified reference. This may have occurred to due a previously executed pipeline action that deleted the object with the corresponding reference.

Action: Check the pipeline message flow configuration to make sure there is no pipeline action that deletes the object with the specified reference that executes prior to this error

Level: 1

Type: ERROR

Impact: Data

OSB-382007: Failed to start timer {0}: {1}

Cause: There was an unexpected error while collecting statistics in OSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382008: Failed to lookup counter {0}

Cause: There was an unexpected error while collecting statistics in OSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382009: Failed to increment counter {0}: {1}

Cause: There was an unexpected error while collecting statistics in OSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382010: Failed to stop timer {0}: {1}

Cause: There was an unexpected error while collecting statistics in OSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382012: Expected object of type java.lang.Throwable, instead found: {0}

Cause: An unexpected error has occurred in OSB pipeline runtime while processing the response message from a business service.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382013: The configurations for the proxy service is in flux.

Cause: The processing of the message has failed in OSB runtime due to the fact that the configurations for the proxy service is in flux. This proxy is unable to send an outbound message to service "{0}" until the configuration stabilizes.

Action: Wait until the configuration of OSB server stabilizes and retry sending the request.

Level: 1

Type: ERROR

Impact: Process

OSB-382014: The configurations for the proxy and target services are in flux. This proxy is unable to route to service "{0}" until the configuration stabilizes.

Cause: The processing of the message has failed in OSB runtime due to the fact that the configurations for the proxy and target services are in flux. This proxy is unable to send an outbound message to service "{0}" until the configuration stabilizes.

Action: Wait until the configuration of OSB server stabilizes and retry sending the request.

Level: 1

Type: ERROR

Impact: Process

OSB-382015: Cannot create RouterContext for non-proxy services: {0}

Cause: There was an internal error while initializing the OSB pipeline runtime state for given service. Only proxy service can process inbound messages

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382016: Failed to instantiate router for service {0}: {1}

Cause: There was an error while initializing the OSB pipeline runtime state for given proxy service. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382017: Failed to find runtime object for this service: {0}

Cause: There was an unexpected error while initializing the OSB pipeline runtime state for given service.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382018: Unable to generate runtime for router configuration: {0}

Cause: This is a diagnostic error message that is logged with error severity in the event OSB pipeline runtime fails to initialize its state. The message will contain various bits of information that will help in the analysis of the underlying cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382020: Failed to register the stage action {0}: {1}

Cause: There was an error during the initialization and/or registration of single pipeline action {0}. This may happen due to incorrectly configured installation of OSB product

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-382021: Failed to register the stage-action application {0}: {1}

Cause: There was an error during the initialization and/or registration of a set of pipeline actions contained in an application file {0}. This may happen due to incorrectly configured installation of OSB product

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-382022: Failed to load factory class: {0}

Cause: There was an error during the initialization and/or registration of a set of pipeline actions. This may happen due to incorrectly configured installation of OSB product

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-382023: Failed to instantiate instance of action factory: {0}

Cause: There was an error during the initialization and/or registration of a set of pipeline actions. This may happen due to incorrectly configured installation of OSB product

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-382024: Failed to instantiate instance of action factory (constructor may not be public): {0}

Cause: There was an error during the initialization and/or registration of a set of pipeline actions. This may happen due to incorrectly configured installation of OSB product

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-382025: Transformation from {0} to {1} is not supported

Cause: An error has occured while transforming the message payload from one type (e.g. MFL) to another (e.g. XML). This may happen some transport requires the payload in certain form in order to send an outbound request and OSB runtime has no way to convert payload in its current form to desired form

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382028: Failed to load WSDL binding information for service

Cause: There was an unexpected error during the processing of the message by OSB pipeline runtime. The error happened while trying to load WSDL binding information for proxy service.

Action: Check configuration of proxy service and contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382029: Failed to create WS-I compliance checker

Cause: There was an unexpected error during the processing of the message by OSB pipeline runtime. The error happened during initialization of component that checks for WS-I compliance.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382030: Failure while un-marshalling message: {0}

Cause: There was an error parsing request or response payload. E.g. the request payload may have improperly formatted multipart/related data which will lead to an error trying to un-marshall message attachments. There will be an error message that will point to specific cause of the error

Action: Look at the specific error message and examine the payload to see why OSB fails to un-marshall its contents properly.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382032: The message must be an instance of: {0}

Cause: There was an error parsing the contents of request or response message due to the fact that the payload was expected to contain a valid SOAP envelope but did not. This can happen for when a SOAP (Any SOAP or WDSL-based OSB proxy receives a request message that does not contain a valid SOAP envelope

Action: Examine the payload to make sure it contains valid SOAP envelope

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382033: A soap:Envelope must contain a soap:Body

Cause: There was an error parsing the contents of request or response message due to the fact that the payload was expected to contain a valid SOAP Body within SOAP Envelope but did not. This can happen for when a SOAP (Any SOAP or WDSL-based OSB proxy receives a request message that does not contain a valid SOAP Body element in its envelope

Action: Examine the payload to make sure it contains valid SOAP Body element

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382034: Expected SOAP 1.1 Envelope

Cause: There was an error during the conversion of SOAP 1.1 payload to SOAP 1.2 payload. The expected SOAP 1.1 Envelope element was missing.

Action: Make sure the payload is valid SOAP 1.1 payload. One can use Log action to log and examine the contents of any message context variable, including $body

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382035: There was an error during the conversion of SOAP 1.1 payload to SOAP 1.2 payload. The expected SOAP 1.1 Header element was missing.

Cause: There was an error during the conversion of SOAP 1.1 payload to SOAP 1.2 payload. The expected SOAP 1.1 Header element was missing.

Action: Make sure the payload is valid SOAP 1.1 payload. One can use Log action to log and examine the contents of any message context variable, including $body

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382036: There was an error during the conversion of SOAP 1.1 payload to SOAP 1.2 payload. The expected SOAP 1.1 Body element was missing.

Cause: There was an error during the conversion of SOAP 1.1 payload to SOAP 1.2 payload. The expected SOAP 1.1 Body element was missing.

Action: Make sure the payload is valid SOAP 1.1 payload. One can use Log action to log and examine the contents of any message context variable, including $body

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382037: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Envelope element was missing.

Cause: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Envelope element was missing.

Action: Make sure the payload is valid SOAP 1.2 payload. One can use Log action to log and examine the contents of any message context variable, including $body

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382038: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Header element was missing.

Cause: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Header element was missing.

Action: Make sure the payload is valid SOAP 1.2 payload. One can use Log action to log and examine the contents of any message context variable, including $body

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382039: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Body element was missing.

Cause: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Body element was missing.

Action: Make sure the payload is valid SOAP 1.2 payload. One can use Log action to log and examine the contents of any message context variable, including $body

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382040: Failed to set the value of context variable "{0}". Value must be an instance of {1}.

Cause: There was an error assigning a value to specified message context variable. There are certain message context variables, e.g. $outbound, $attachments, $fault that have a pre-defined structure (see online OSB documentation for details) and any value assigned to them is expected to be in certain format

Action: Use OSB Log action to verify that the value being assigned to the variable is in fact in expected format

Level: 1

Type: ERROR

Impact: Data

OSB-382041: Failed to set the value of context variable "{0}". Variable is read-only.

Cause: There was an error assigning a value to specified message context variable. There are certain message context variables, e.g $operation that one cannot assign values to and thus they are considered read-only.

Action: Check OSB on-line documentation to make sure that the variable whose value is being changed is not considered a read-only variable.

Level: 1

Type: ERROR

Impact: Data

OSB-382042: Failed to set the value of context variable "{0}". {1}

Cause: There was an error assigning a value to specified message context variable. This may happen when trying to assign non-XML values to message context variables that expect XML content (e.g. $fault).

Action: Use OSB Log action to verify that the value being assigned to the variable is in fact in expected format

Level: 1

Type: ERROR

Impact: Data

OSB-382043: Failed to update the value of context variable "{0}": {1}

Cause: There was an error assigning or updating a value of a specified message context variable. This may happen when the value being assigned does not conform to specified format for a system variable (e.g. setting $outbound to null) or updating a read-only portion of a variable (e.g. changing 'service' element of $inbound) message context variable

Action: Use OSB Log action to verify that the value being assigned to the variable is in fact in expected format. Also check OSB on-line documentation to make sure that the part of the variable that you are changing is not considered read-only.

Level: 1

Type: ERROR

Impact: Data

OSB-382045: Failed to initialize the value of context variable "{0}": {1}

Cause: There was an unexpected error while initializing one of the system variables. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382046: Failed to marshall the value of context variable "{0}" to XML: {1}

Cause: There was an error retrieving the XML representation of the value of a system context variable, e.g. request or response meta-data for $inbound or $outbound message context variable. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382047: Processor must be in INACTIVE state

Cause: There was an internal error in OSB pipeline runtime while processing the inbound request by a proxy service. The state of OSB pipeline was not expected

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382048: Processor must be in RESPONSE or ERROR state

Cause: There was an internal error in OSB pipeline runtime while processing the inbound request by a proxy service. The state of OSB pipeline was not expected

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382049: OSB failed to start a transaction

Cause: There was an internal error in OSB pipeline runtime while processing the inbound request by a proxy service. The state of OSB pipeline was not expected

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382050: Expected active transaction, actual transaction status: {0}

Cause: There was an internal error in OSB pipeline runtime while processing the inbound request by a proxy service. The state of OSB pipeline was not expected

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382051: No transaction found on the current thread

Cause: There was an internal error in OSB pipeline runtime while processing the inbound request by a proxy service. The state of OSB pipeline was not expected

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382052: Cannot commit a different transaction

Cause: There was an internal error in OSB pipeline runtime while processing the inbound request by a proxy service. The state of OSB pipeline was not expected

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382053: Cannot rollback a different transaction

Cause: There was an internal error in OSB pipeline runtime while processing the inbound request by a proxy service. The state of OSB pipeline was not expected

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382054: Expected [[http://www.bea.com/wli/sb/context]java-content] element under $body is missing or invalid

Cause: Services of Messaging Type : Java are expected to contain a valid [[http://www.bea.com/wli/sb/context]java-content] child element under $body.

Action: Make sure the contents of $body conforms to expected format. One can use Log action to log and examine the contents of any message context variable, including $body

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382100: Failure in binding-layer while processing inbound request for service {0}: {1}

Cause: There was an error in OSB pipeline runtime while processing the inbound request by a proxy service. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382101: Failure in binding-layer while preparing inbound response for service {0}: {1}

Cause: There was an error in OSB pipeline runtime while preparing the inbound response for a proxy service. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382102: Failure in binding-layer while preparing outbound request for service {0}: {1}

Cause: There was an error in OSB pipeline runtime while preparing the outbound request for a business service. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382103: Failure in binding-layer while processing outbound response for service {0}: {1}

Cause: There was an error in OSB pipeline runtime while processing the outbound response from a business service. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382104: Failed to prepare request metadata for service {0}: {1}

Cause: There was an error in OSB pipeline runtime while processing the request metadata for either $inbound or $outbound message context variable. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382105: Failed to prepare response metadata for service {0}: {1}

Cause: There was an error in OSB pipeline runtime while processing the response metadata for either $inbound or $outbound message context variable. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382110: There was an error while encoding base64 content

Cause: An unexpected error has occurred in OSB pipeline runtime while performing XOP/MTOM-related processing of inbound message. There should be an error message that describes specific error cause

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382111: Missing ref attribute from binary-content element

Cause: A binary-content element is not properly constructed - it is missing a required ref attribute

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382112: No object is registered for ref ''{0}'' in source repository

Cause: An error has occurred in OSB pipeline runtime while processing the response message for specified proxy service due to an attempt to look up an object in source repository with the specified reference.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382113: Missing or illegal value for Content-ID MIME header in MimeSource

Cause: An error has occurred in OSB pipeline runtime while performing XOP/MTOM processing for outbound request message

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382114: Could not decode URI ''{0}''. {1}

Cause: An error has occurred in OSB pipeline runtime while performing XOP/MTOM processing for inbound request message There should be precise error message that points to the cause of the error

Action: Make sure that the inbound XOP/MTOM payload is valid according to XOP/MTOM standard

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382115: Encountered XOP:Include SOAP Element without an href. Without the href, we cannot lookup its MIME attachment !

Cause: An error has occurred in OSB pipeline runtime while performing XOP/MTOM processing for inbound request message

Action: Make sure that the inbound XOP/MTOM payload is valid according to XOP/MTOM standard

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382116: There should be exactly one MIME attachment with Content-ID = ''{0}''.

Cause: An error has occurred in OSB pipeline runtime while performing XOP/MTOM processing for inbound request message

Action: Make sure that the inbound XOP/MTOM payload is valid according to XOP/MTOM standard

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382117: Received more than one ''Content-Transfer-Encoding'' MIME header in attachment with CID ''{0}'', received {1}

Cause: An error has occurred in OSB pipeline runtime while performing XOP/MTOM processing for inbound request message

Action: Make sure that the inbound XOP/MTOM payload is valid according to XOP/MTOM standard

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382118: Decoding of MIME attachments from MIME Content-Transfer-Encoding=''{0}'' not supported

Cause: An error has occurred in OSB pipeline runtime while performing XOP/MTOM processing for inbound request message

Action: Make sure that the inbound XOP/MTOM payload is valid according to XOP/MTOM standard

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382119: A service not enabled for XOP/MTOM has received an XOP/MTOM message

Cause: A service not enabled for XOP/MTOM has received an XOP/MTOM message

Action: Make sure that the proxy service has XOP/MTOM feature enabled to allow it to properly process incoming payload

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382120: Mixing of XOP/MTOM and attachments is not allowed!

Cause: An outbound request to a service enabled for XOP/MTOM cannot be prepared due to the fact that the business service is enabled for XOP/MTOM support and the value of $attachments variable is not null. Mixing of XOP/MTOM and attachments is not supported

Action: Please make sure that $attachments variable does not contain any information when routing to XOP/MTOM-enabled services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382121: Each MIME part that is referred to by xop:Include MUST have a Content-Transfer-Encoding header field

Cause: An error has occurred in OSB pipeline runtime while performing XOP/MTOM processing for inbound request message

Action: Make sure that the inbound XOP/MTOM payload is valid according to XOP/MTOM standard

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382150: Failure while dispatching request to service {0}: {1}

Cause: There was an unexpected error in OSB pipeline runtime while performing an outbound request for either routing, publish or service callout action. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382151: Nothing is known about service {0}

Cause: There was an unexpected error retrieving configuration details for specified service {0}.

Action: Use OSB console to check that the service in question is properly configured

Level: 1

Type: ERROR

Impact: Configuration

OSB-382153: Cannot delete system variable "{0}" from context

Cause: An attempt to delete a system variable from the message context failed because there are a number of system variables that cannot be deleted, such as $inbound and $outbound.

Action: Check OSB online documentation on whether a given system variable can be deleted from the message context.

Level: 1

Type: ERROR

Impact: Data

OSB-382187: Could not roll back the action for delete resequencer configuration {0}: {1}

Cause: Could not roll back the action for delete resequencer configuration. Please check the exception message.

Action: Please check the exception message. It may indicate the source of error.

Level: 1

Type: ERROR

Impact: Process

OSB-382188: Could not roll back the action for create resequencer configuration {0}: {1}

Cause: Could not roll back the action for create resequencer configuration. Please check the exception message.

Action: Please check the exception message. It may indicate the source of error.

Level: 1

Type: ERROR

Impact: Process

OSB-382189: Could not load the resequencer configuration for pipeline {0}: {1}

Cause: Could not load the resequencer configuration. Please check the exception message.

Action: Please check the exception message. It may indicate the source of error.

Level: 1

Type: ERROR

Impact: Configuration

OSB-382190: Component {0} may not be invoked because it exists in a different project

Cause: Invoked components (pipeline and split join resources) must be in the same project as the proxy service invoking them

Action: Check the proxy service configuration and wire it as needed

Level: 1

Type: ERROR

Impact: Configuration

OSB-382191: {0}: Unhandled error caught by system-level error handler: {1}

Cause: A error has occurred during message processing and was not handled via the user-configured error handler

Action: Check the exception message. It will indicate the source of error.

Level: 1

Type: ERROR

Impact: Process

OSB-382500: OSB Service Callout action received SOAP Fault response

Cause: OSB Service Callout action has received a SOAP Fault response from the web service that was invoked. The contents of the received SOAP Fault can be seen in the details element of $fault message context variable.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382501: OSB Service Callout action received an unrecognized response

Cause: The service invoked by OSB Service Callout action has returned payload that was not consistent with the declared service binding type and as a result could not be properly parsed by OSB. For example, this can happen if a service that was registered with XML binding type, returned non well-formed XML payload. The contents of the received response can be seen in the details element of $fault message context variable.

Action: Check the contents of response payload in $fault variable to see why it is inconsistent with the declared service binding type

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382502: OSB Service Callout action received an error response

Cause: The service invoked by OSB Service Callout action has indicated that an error condition other than a SOAP fault has occured. For example, this may happen when an HTTP 404 (Page Not Found) error code is received from an external HTTP service. The contents of the received response (if any) can be seen in the details element of $fault message context variable.

Action: Check the contents of response payload in $fault variable to see what the problem with service invocation is

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382505: OSB Validate action failed validation

Cause: The input expression has failed validation according to provided schema resource. The details of the validation error, such as specific error message, location of the invalid XML, etc. can be seen in the details element of $fault message context variable

Action: Check the contents of $fault variable to see the source of the validation failure

Level: 1

Type: ERROR

Impact: Data

OSB-382510: OSB Assign action failed updating variable "{0}": {1}

Cause: There was an error during the evaluation of XQuery/XSLT expression during the execution of Assign action. This could happen if an XQuery expression the result of which is being assigned to a variable, results in a runtime error from the XQuery evaluation engine. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured XQuery expression for potential syntactic or semantic problems

Level: 1

Type: ERROR

Impact: Data

OSB-382511: OSB Delete action failed updating variable "{0}": {1}

Cause: There was an error during the execution of Delete action. This could happen if the specified XPath expression is not a valid expression or results in a runtime error from XPath evaluation engine. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured XPath expression for potential syntactic or semantic problems

Level: 1

Type: ERROR

Impact: Data

OSB-382512: OSB Insert action failed updating variable "{0}": {1}

Cause: There was an error during the execution of Insert action. This could happen if an XQuery expression the result of which is being inserted into a variable, results in a runtime error from the XQuery evaluation engine. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured XQuery expression for potential syntactic or semantic problems

Level: 1

Type: ERROR

Impact: Data

OSB-382513: OSB Replace action failed updating variable "{0}": {1}

Cause: There was an error during the execution of Replace action. This could happen if an XQuery expression the result of which is being replaced in a variable, results in a runtime error from the XQuery evaluation engine. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured XQuery expression for potential syntactic or semantic problems

Level: 1

Type: ERROR

Impact: Data

OSB-382514: OSB Rename action failed updating variable "{0}": {1}

Cause: There was an error during the execution of Rename action. This could happen if the specified XPath expression is not a valid expression or results in a runtime error from XPath evaluation engine. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured XPath expression for potential syntax or semantic problems

Level: 1

Type: ERROR

Impact: Data

OSB-382515: Callout to java method "{0}" resulted in exception: {1}

Cause: Java method specified in Java Callout action was invoked and resulted in an exception. The exception details should be part of the error message.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382516: Failed to evaluate expression for callout to java method "{0}". Argument index: {1}, exception: {2}

Cause: There was an error evaluating one or more arguments to a Java callout method. This could happen if an XQuery expression the result of which is being used as an argument to java method, results in a runtime error from the XQuery evaluation engine. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured XQuery expression for potential syntactic or semantic problems

Level: 1

Type: ERROR

Impact: Data

OSB-382517: Failed to assign the result of java callout to variable. Method: {0}, variable: {1}, exception: {2}

Cause: There was an error while assigning the result of invoked Java method to specified message context variable. This could happen if the variable being assigned to is a read-only system variable (e.g. $operation), or a system variable whose type does not match that returned by the invoked Java method. There should be a specific error message that will pinpoint the source of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382518: Security exception while calling to java method "{0}". Service account: {1}. {2}

Cause: There was an error while setting up the security context for java callout method. This could happen if there is a problem retrieving the credentials of specified service account. There should be a specific error message that will pinpoint the source of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382519: The XmlObject returned by a java callout must be a simple type, an attribute or an element.

Cause: Java method invoked returned an unsupported type of XML Bean. The only supported types are simple types, attributes or element.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382520: Unexpected error executing if-then-else expression

Cause: An unexpected runtime exception has occured during the execution of the if-then-else action.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382521: Variable targeted for rename is not XML or MFL

Cause: The variable that is targeted for rename operation does not hold XML data.

Action: Check the value of the variable that is targeted for rename operation. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382522: Variable targeted for replace is not XML or MFL

Cause: The variable that is targeted for replace operation does not hold XML data.

Action: Check the value of the variable that is targeted for rename operation. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382523: The outbound variable has not been initialized

Cause: This is an unexpected error that occured due to incorrect state of the pipeline at runtime

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382524: Failed to perform validation

Cause: An unexpected runtime error has occured during the execution of validate action. There should be a specific error message that will pinpoint the source of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382525: Variable targeted for validate is not XML or MFL

Cause: The variable that is targeted for validate operation does not hold XML data.

Action: Check the value of the variable that is targeted for validate operation. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382526: Variable targeted for insert is not XML or MFL

Cause: The variable that is targeted for insert operation does not hold XML data.

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382527: Inserting the result of this expression will create an invalid (multi-rooted) document

Cause: Inserting the result of this expression will create an invalid (multi-rooted) document. One way this could happen is if ones tries to insert (some) element node before . in $body message context variable

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382528: Failed to insert after

Cause: Inserting the result of this expression after specified XPath resulted in an error.

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382529: Cannot insert as a child of an attribute

Cause: It is illegal to insert as a child of an attribute

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382530: Unable to insert after first child

Cause: Unable to insert after first child as there was no child elements of specified XPath expression

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382531: Unable to insert after last child

Cause: Unable to insert after child element

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382532: Only attributes may be inserted next to another attribute

Cause: Only attributes may be inserted next to another attribute

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382533: Only elements and simple values may be inserted next to or inside of another element

Cause: Only elements and simple values may be inserted next to or inside of another element

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382534: Content targeted for replace is not an element or an attribute

Cause: Content targeted for replace is not an element or an attribute

Action: Check the value of the variable that is targeted for replace operation. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382535: An attribute may only be replaced with an attribute

Cause: An attribute may only be replaced with an attribute

Action: Check the value of the variable that is targeted for replace operation. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382536: An element or its contents may only be replaced with elements and simple values

Cause: An element or its contents may only be replaced with elements and simple values

Action: Check the value of the variable that is targeted for replace operation. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382537: Invalid SOAP RPC document - part "{0}" is not defined in the WSDL definitions.

Cause: The response to service callout contained invalid data according to WSDL definition of the service being invoked.

Action: Check the response payload of service invocation and make sure it conforms to the WSDL definitions for the service. The contents of the received response can be seen in the details element of $fault message context variable.

Level: 1

Type: ERROR

Impact: Data

OSB-382538: Invalid SOAP RPC document - part {0} occurs more than once.

Cause: The response to service callout contained invalid data according to WSDL definition of the service being invoked.

Action: Check the response payload of service invocation and make sure it conforms to the WSDL definitions for the service. The contents of the received response can be seen in the details element of $fault message context variable.

Level: 1

Type: ERROR

Impact: Data

OSB-382539: Invalid SOAP RPC document - part {0} contains more than one XML element

Cause: The response to service callout contained invalid data according to WSDL definition of the service being invoked.

Action: Check the response payload of service invocation and make sure it conforms to the WSDL definitions for the service. The contents of the received response can be seen in the details element of $fault message context variable.

Level: 1

Type: ERROR

Impact: Data

OSB-382540: Unexpected error - invalid internal state occured during the execution of service callout action

Cause: An unexpected error had occured during the execution of service callout action

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382541: Invalid SOAP RPC document - part "{0}" is required but not present.

Cause: The response to service callout contained invalid data according to WSDL definition of the service being invoked.

Action: Check the response payload of service invocation and make sure it conforms to the WSDL definitions for the service. The contents of the received response can be seen in the details element of $fault message context variable.

Level: 1

Type: ERROR

Impact: Data

OSB-382542: The Transport Mode is set to "request-only". A Service Callout only supports "request-response" communications.

Cause: The Transport Mode is set to "request-only". Service Callout action only supports "request-response" communications.

Action: Check the contents of $outbound message context variable to make sure the transport mode element is set properly. One can use Log action to see the contents of any message context variable at runtime

Level: 1

Type: ERROR

Impact: Configuration

OSB-382543: Invalid message: the SOAP Header value is not an XML instance

Cause: The value of the message context variable used to set SOAP headers for service callout action does not contain valid XML

Action: Check the contents of specified message context variable to make sure it is set properly. One can use Log action to see the contents of any message context variable at runtime

Level: 1

Type: ERROR

Impact: Data

OSB-382544: Invalid message: the message is not an XML instance

Cause: The value of the message context variable used to set SOAP body for service callout action does not contain valid XML

Action: Check the contents of specified message context variable to make sure it is set properly. One can use Log action to see the contents of any message context variable at runtime

Level: 1

Type: ERROR

Impact: Data

OSB-382545: Unexpected error - the part schema type cannot be found

Cause: An unexpected error had occured during the execution of service callout action during the parsing phase of the service callout response

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382546: Unexpected error - mismatch between configuration and WSDL definition

Cause: An unexpected error had occured during the execution of service callout action during the parsing phase of the service callout response

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-382547: The value for part "{0}" is not valid. An XML Element is expected.

Cause: An error had occured during the execution of service callout action during the phase when an outbound request payload gets constructed due to the fact that the configured message context variable does not contain valid XML element.

Action: Check the contents of specified message context variable to make sure it is set properly. One can use Log action to see the contents of any message context variable at runtime

Level: 1

Type: ERROR

Impact: Data

OSB-382548: Unable to find the type definition of the part {0}

Cause: An error had occured during the execution of service callout action during the phase when an outbound request payload gets constructed due to missing or invalid type information in WSDL definitions

Action: Check the registered WSDL definition for proper semantic type information for the part in question

Level: 1

Type: ERROR

Impact: Data

OSB-382549: Error accessing information from the target WSDL service

Cause: An error had occured during the execution of service callout action during the phase when an outbound request payload gets constructed due to not being able to access service WSDL definition. There should be a specific message that will point to the cause of the error.

Action: Check that the corresponding WSDL definition is properly registered

Level: 1

Type: ERROR

Impact: Configuration

OSB-382550: Setting quality of service to 'Exactly Once' in service callout action is not supported for service {0}

Cause: Setting quality of service to 'Exactly Once' in service callout action is not supported for selected service. Quality of service can be set to 'Exactly Once' only if the service transport endpoint is Transactional and the message pattern is 'one-way' or 'synchronous'.

Action: Check the pipeline configuration to make sure that the quality of service is not set to 'Exactly Once' via Routing Options or some other action that changes the contents of $outbound message context variable. You can use Log action to see the value of any message context variable at runtime.

Level: 1

Type: ERROR

Impact: Configuration

OSB-382551: XQuery expression did not return the non-empty source to apply the MFL translation.

Cause: XQuery expression did not return the non-empty source to apply the MFL translation.

Action: Check the XQuery expression to make sure that it returns a non-empty input to apply the MFL translation. You can use Log action to see the value of XQuery expression at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382552: Binary content reference {0} is not valid.

Cause: Binary content reference is not valid. It should be inserted by the pipeline as a result of passing binary content to the pipeline.

Action: Check the binary-content ref attribute on which the MFL translation is applied. binary-content element should be inserted as a result of passing binary content to the pipeline. You can use Log action to see the value of this ref attribute at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382553: Input to non-xml to xml MFL translation is invalid.

Cause: Input to the transformation should be non-empty text or the binary data represented by binary-content element in the pipeline. XML input is not allowed.

Action: Make sure that input expression returns the text or the binary-content ref attribute inserted by the pipeline as a result of passing binary content to the OSB. You can use Log action to see the value of this expression at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382554: XQuery expression evaluates to an invalid MFL resource name {0}.

Cause: XQuery expression did not return the valid MFL resource name. It should evaluate to an existing mfl resource in the OSB at runtime.

Action: Make sure that XQuery expression should evaluate to a existing mfl resource in the OSB at runtime. You can use Log action to see the value of this expression at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382555: XML to Binary MFL translation failed for the MFL Resource {0} : {1}

Cause: XML to Binary MFL translation failed. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured mfl resource and the input data for potential syntactic or semantic problems.

Level: 1

Type: ERROR

Impact: Data

OSB-382556: Binary to XML MFL translation failed for the MFL Resource {0} : {1}

Cause: Binary to XML MFL translation failed. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured mfl resource and the input data for potential syntactic or semantic problems.

Level: 1

Type: ERROR

Impact: Data

OSB-382557: No source was found in source repository with ref ''{0}''.

Cause: No source was found in source repository with ref ''{0}'', which was the result of configured XQuery expression

Action: Check the XQuery expression to make sure that it returns proper result. You can use Log action to see the value of an XQuery expression at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382558: Dynamic validate query must return a single instance of {0}

Cause: The configured XQuery expression did not evaluate to a single instance of expected XML snippet in format "ctx:validate...".

Action: Please see online documentation for details of the expected format and check the configured XQuery expression for potential syntactic or semantic problems

Level: 1

Type: ERROR

Impact: Data

OSB-382559: XQuery expression did not return the non-empty source to apply the nXSD translation.

Cause: XQuery expression did not return the non-empty source to apply the nXSD translation.

Action: Check the XQuery expression to make sure that it returns a non-empty input to apply the nXSD translation. You can use Log action to see the value of XQuery expression at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382560: Binary content reference {0} is not valid.

Cause: Binary content reference is not valid. It should be inserted by the pipeline as a result of passing binary content to the pipeline.

Action: Check the binary-content ref attribute on which the nXSD translation is applied. binary-content element should be inserted as a result of passing binary content to the pipeline. You can use Log action to see the value of this ref attribute at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382561: Input to native to XML nXSD translation is invalid.

Cause: Input to the translation should be non-empty text or the binary data represented by binary-content element in the pipeline. XML input is not allowed.

Action: Make sure that input expression returns the text or the binary-content ref attribute inserted by the pipeline as a result of passing binary content to the OSB. You can use Log action to see the value of this expression at runtime.

Level: 1

Type: ERROR

Impact: Other

OSB-382562: XQuery expression evaluates to an invalid nXSD {0}.

Cause: XQuery expression did not return the valid nXSD. It should evaluate to an existing nXSD schema in the OSB at runtime.

Action: Make sure that XQuery expression should evaluate to a existing nXSD schema in the OSB at runtime. You can use Log action to see the value of this expression at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-382563: XML to Native nXSD translation failed for the nXSD {0} : {1}

Cause: XML to Native nXSD translation failed. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured nXSD resource and the input data for potential syntactic or semantic problems.

Level: 1

Type: ERROR

Impact: Data

OSB-382564: Native to XML nXSD translation failed for the nXSD {0} : {1}

Cause: Native to XML nXSD translation failed. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured nXSD resource and the input data for potential syntactic or semantic problems.

Level: 1

Type: ERROR

Impact: Data

OSB-382565: nXSD ref {0} does not exist.

Cause: nXSD ref does not exist.

Action: Make sure that the nXSD ref exists in OSB configuration.

Level: 1

Type: ERROR

Impact: Data

OSB-382566: Error in applying translation to the input for nXSD {0} : {1}

Cause: Error in applying nXSD translation to the input.

Action: Make sure that input nXSD is well formed. Please refer to error message for more debug details.

Level: 1

Type: ERROR

Impact: Data

OSB-382567: Invalid message: the Attachments value is not an XML instance

Cause: The value of the message context variable used to set attachments for service callout action does not contain valid XML

Action: Check the contents of specified message context variable to make sure it is set properly. One can use Log action to see the contents of any message context variable at runtime

Level: 1

Type: ERROR

Impact: Data

OSB-382600: Dynamic publish query must return a single instance of {0}

Cause: The configured XQuery expression did not evaluate to a single instance of expected XML snippet in format \"ctx:route...\".

Action: Please see online documentation for details of the expected format and check the configured XQuery expression for potential syntactic or semantic problems

Level: 1

Type: ERROR

Impact: Data

OSB-382601: Error during dynamic publish action: {0}

Cause: A runtime error has occured during the execution of dynamic publish action. This might occur for a variety of reasons, for example, the XQuery/XSLT evaluation of service reference has produced a runtime error or returned an XML element in an unexpected format.

Action: Check the configured XQuery expression for potential syntactic or semantic problems

Level: 1

Type: ERROR

Impact: Data

OSB-382602: Service not specified

Cause: The result of the configured XQuery expression did not contain the expected 'service' element.

Action: Please see online documentation for details of the expected format and check the configured XQuery expression for potential syntactic or semantic problems

Level: 1

Type: ERROR

Impact: Configuration

OSB-382603: Error during publish

Cause: A runtime exception has occured during the execution of the publish action. This may have occured due to an error from the underlying transport. There should be a specific error message that will point the cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382604: Unexpected error executing the publish table expression

Cause: An unexpected runtime exception has occured during the execution of the publish table action.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382605: Publishing to service {0} is not supported because it has result caching enabled

Cause: If a business service is caching it's results, it cannot be published to.

Action: Either remove the result caching configuration from the business service or publish to a different service.

Level: 1

Type: ERROR

Impact: Configuration

OSB-382610: Dynamic route query must return a single instance of {0}

Cause: The configured XQuery expression did not evaluate to a single instance of expected XML snippet in format \"ctx:route...\".

Action: Please see online documentation for details of the expected format and check the configured XQuery expression for potential syntactic or semantic problems

Level: 1

Type: ERROR

Impact: Data

OSB-382611: Service not specified

Cause: The result of the configured XQuery expression did not contain the expected 'service' element.

Action: Please see online documentation for details of the expected format and check the configured XQuery expression for potential syntactic or semantic problems

Level: 1

Type: ERROR

Impact: Configuration

OSB-382612: Error preparing message for dispatch: {0}

Cause: A runtime exception has occured during the preparation of the outbound message for routing node. This may have occured due to an error while executing request actions of the routing node. There should be a specific error message that will point the cause of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382613: Cannot perform routing unless router is in REQUEST state

Cause: This is an unexpected error that occured due to erroneous state of the pipeline

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-382614: Unexpected error executing the routing table expression

Cause: An unexpected runtime exception has occured during the execution of the routing table action.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-382620: XPath expression for key does not yield a text value

Cause: XPath expression does not yield a text value.

Action: Please check the XPath expression.

Level: 1

Type: ERROR

Impact: Other

OSB-382621: Failed to issue report: {0}

Cause: Reporting data manager is not able to process and/or store reporting data in appropriate data store.

Action: Check if the reporting provider is installed properly.

Level: 1

Type: ERROR

Impact: Other

OSB-382630: Failed to generate the alert: {0}

Cause: Failed to generate the alert. There might be a problem with the configured Alert Destination.

Action: Please check the configuration of Alert Destination.

Level: 1

Type: ERROR

Impact: Other

OSB-383500: Failed to deploy pipeline resequencer component for service {0}: {1}

Cause: Resequencer component failed to deploy. Exception details will point to the actual cause.

Action: Please check the resequencer configuration. Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383501: Failed to deploy pipeline resequencer component for service {0} with operation name {1}: {2}

Cause: Resequencer component failed to deploy. Exception details will point to the actual cause.

Action: Please check the resequencer configuration. Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383502: Failed to undeploy pipeline resequencer component for service {0}: {1}

Cause: Resequencer component failed to undeploy. Exception details will point to the actual cause.

Action: Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383503: Failed to deploy pipeline resequencer component for service {0} with operation name {1}: {2}

Cause: Resequencer component failed to undeploy. Exception details will point to the actual cause.

Action: Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383504: Failed to load pipeline resequencer component for service {0}: {1}

Cause: Resequencer component failed to load. Exception details will point to the actual cause.

Action: Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383505: Failed to load pipeline resequencer component for service {0} with operation name {1}: {2}

Cause: Resequencer component failed to load. Exception details will point to the actual cause.

Action: Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383506: Failed to unload pipeline resequencer component for service {0}: {1}

Cause: Resequencer component failed to unload. Exception details will point to the actual cause.

Action: Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383507: Failed to unload pipeline resequencer component for service {0} with operation name {1}: {2}

Cause: Resequencer component failed to unload. Exception details will point to the actual cause.

Action: Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383508: Failed to initialize resequencer: {0}

Cause: Resequencer failed to initialize. Exception details will point to the actual cause.

Action: Please make sure that the DB is running. Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383509: Pipeline ref {0} not found. Message dispatch from resequencer to pipeline will fail: {1}

Cause: Pipeline ref does not exists. Pipeline component may have been deleted.

Action: Please make sure that the pipeline component exists in the OSB configuration.

Level: 1

Type: ERROR

Impact: Other

OSB-383510: Message with id {0} for resequencer component {1} could not be persisted: {2}

Cause: Message could not be persisted. DataBase may be down. Exception details may point to the actual cause.

Action: Please make sure that the DB is running. Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383511: Message with id {0} for resequencer component {1} dispatch failed to Resequencer: {2}.

Cause: Message could not be dispatched to Resequencer. Exception details may point to the actual cause.

Action: Please make sure that the DB is running. Exception message may indicate the exact source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383512: Message with id {0} could not be retrieved: {1}

Cause: Message could not be retrieved. DataBase may be down. Exception details may point to the actual cause.

Action: Please make sure that the DB is running. Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383513: Message with id {0} for resequencer component {1} could not be dispatched to pipeline after resequencing: {2}

Cause: Message could not be dispatched to pipeline after resequencing. Exception details may point to the actual cause.

Action: Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383514: Message with id {0} for resequencer component {1} could not be persisted: {2}

Cause: Message could not be persisted. Exception details may point to the actual cause.

Action: Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383515: Message payload with id {0} for resequencer component {1} could not be read: {2}

Cause: Message could not be read. Exception details may point to the actual cause.

Action: Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383516: Resequencer is not configured for this pipeline.

Cause: Resequencer is not configured for this pipeline. Pipeline component may have been updated to remove resequencer configuration.

Action: Please update the Pipeline configuration.

Level: 1

Type: ERROR

Impact: Other

OSB-383517: Resequencer configuration parsing failed.

Cause: Resequencer configuration parsing failed. Pipeline component may be corrupt.

Action: Please update the Pipeline configuration.

Level: 1

Type: ERROR

Impact: Other

OSB-383518: Pipeline ref {0} not found.

Cause: Pipeline ref does not exists. Pipeline component may have been deleted.

Action: Please make sure that the pipeline component exists in the OSB configuration.

Level: 1

Type: ERROR

Impact: Other

OSB-383519: Invalid variable name {0} in XQuery expression for pipeline component {1}

Cause: Invalid variable name in the XQuery expression for pipeline component.

Action: Please modify the XQuery expression. Valid variables are 'body', 'headers' and 'transportMetaData'

Level: 1

Type: ERROR

Impact: Other

OSB-383520: XQuery expression execution failed for pipeline {0}: {1}

Cause: XQuery expression execution failed. Please check the exception message.

Action: Please check the exception message. It may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383521: XQuery expression {0} evaluated to a null value.

Cause: XQuery expression evaluated to a null value.

Action: Turn on tracing to check the data. Check the data expression for the given transformation. An empty result may be due to missing XML elements/attributes in the data, improper use of namespaces...

Level: 1

Type: ERROR

Impact: Other

OSB-383522: XQuery expression {0} evaluated to an array value.

Cause: XQuery expression evaluated to an array value.

Action: Turn on tracing to check the data. Check the data expression for the given transformation. Such result may happen for example if the selected XML elements/attributes correspond to repeating nodes (XML Schema maxOccurs > 1).

Level: 1

Type: ERROR

Impact: Other

OSB-383523: Resequencer validation failed: {0}

Cause: Resequencer validation failed.

Action: Please check the exception message. It may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383524: XQuery variable {0} could not be retrieved for message id {1}: {2}

Cause: XQuery variable could not be retrieved.

Action: Please check the XQuery expression. Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-383525: XQuery {0} evaluated to unknown type {1}

Cause: XQuery evaluated to unknown type.

Action: Please check the XQuery expression.

Level: 1

Type: ERROR

Impact: Other

OSB-383526: Resequencer could not be stopped successfully: {0}

Cause: Resequencer could not be stopped successfully.

Action: Please check the error message.

Level: 1

Type: ERROR

Impact: Other

OSB-383527: Resequencer message {0} deletion failed after successful execution: {0}

Cause: Resequencer message could not be deleted after successful execution.

Action: Please check the error message.

Level: 1

Type: ERROR

Impact: Other

OSB-383528: Resequencer message {0} targeted to resequencer component {1} doesn't contain the operation name in the dispatch context. Possible cause is, operation name may not be part of the wsdl definition.

Cause: Operation name may not be part of the wsdl definition. It should be one way operation as defined in the wsdl.

Action: Please check the SOAP message. It should have one way operation as defined in the wsdl.

Level: 1

Type: ERROR

Impact: Other

OSB-383529: Resequencer message {0} targeted to resequencer component {1} doesn't contain the valid operation name: {2}. Possible cause is, operation name may not be part of the wsdl definition.

Cause: Operation name may not be part of the wsdl definition. It should be one way operation as defined in the wsdl.

Action: Please check the SOAP message. It should have one way operation as defined in the wsdl.

Level: 1

Type: ERROR

Impact: Other

OSB-383530: Failed to update the resequencer global configuration parameters: {0}

Cause: Resequencer failed to update the global configuration parameters. Exception details will point to the actual cause.

Action: Please make sure that the DB is running. Exception message may indicate the source of error.

Level: 1

Type: ERROR

Impact: Other

OSB-386000: General security error

Cause: General security error

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386003: Mapped service account "{0}" is invalid: user mapping entry for local user "{1}" maps to non-existing remote user "{2}"

Cause: Map the local user to a valid remote user.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386004: Message-level access control denied access to proxy service {0}, operation {1}, subject: {2}

Cause: Message-level access denied.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386005: Mapped service account "{0}" is invalid: its anonymous mapping maps to a non-existing remote user

Cause: Update the service account to map to a valid remote user.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386006: An error occurred while initializing {0}

Cause: Failed to initialize the component.

Action: Contact Oracle Support Services

Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-386007: ResourceIdManager.registerResourceType() failed

Cause: Failed to register the resource.

Action: Contact Oracle Support Services

Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-386008: Message level username/password authentication failed: {0}

Cause: Message level username/password authentication failed.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386009: Message level custom token authentication failed: {0}

Cause: Message level custom token authentication failed.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386010: Internal error: the proxy service is configured for message-level custom token or custom username/password authentication but WS-Security authentication has already taken place.

Cause: WS-Security authentication and message-level custom authentication are mutually exclusive.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386011: An error occurred while evaluating the custom authentication token XPath selector: {0}

Cause: Error evaluating the custom authentication token XPath selector.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386012: An error occurred while evaluating the message-level username XPath selector: {0}

Cause: Error evaluating the message-level username XPath selector.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386013: An error occurred while evaluating the message-level password XPath selector: {0}

Cause: Error evaluating the message-level password XPath selector.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386014: the result of the XPath selector is empty

Cause: the result of the XPath selector is empty

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386015: the XPath selector returned multiple nodes

Cause: the XPath selector returned multiple nodes

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386016: the result of the XPath cannot be converted to java.lang.String (it is not a single text-node or attribute value)

Cause: the result of the XPath cannot be converted to java.lang.String (it is not a single text-node or attribute value)

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386017: the XPath cannot be evaluated because the request message does not have the required message part ({0})

Cause: the XPath cannot be evaluated because the request message does not have the required message part.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386018: an error occurred while evaluating the XPath expression: {0}

Cause: an error occurred while evaluating the XPath expression.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386019: The proxy service operation selection algorithm returned an invalid operation name: {0}

Cause: The proxy service operation selection algorithm returned an invalid operation name.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386020: the xpath result is not within the scope of the root node ({0}), this can happen if the xpath uses the '//' construct.

Cause: You must update your xpath to make sure it only selects elements within the root node (i.e. header or body).

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386021: No resource data

Cause: The resource data parameter was not supplied or is empty.

Action: Specify valid resource data.

Level: 1

Type: ERROR

Impact: Security

OSB-386022: No resource type

Cause: The resource type information was not supplied.

Action: Specify a valid resource type.

Level: 1

Type: ERROR

Impact: Security

OSB-386023: No resource identifier

Cause: The resource identifier parameter was not supplied or is empty.

Action: Specify a valid resource identifier.

Level: 1

Type: ERROR

Impact: Security

OSB-386024: No resource keys found

Cause: No resource key information was supplied in the resource identifier.

Action: Specify a valid resource identifier.

Level: 1

Type: ERROR

Impact: Security

OSB-386025: Invalid data type for {0} resource key value

Cause: The data type of a resource key value is not valid.

Action: Specify a valid resource key data type value.

Level: 1

Type: ERROR

Impact: Security

OSB-386026: Invalid resource type: "{0}"

Cause: An invalid or unknown resource type was supplied.

Action: Specify a valid resource type.

Level: 1

Type: ERROR

Impact: Security

OSB-386027: Expected resource type: {0}

Cause: The resource type supplied did not match the expected type.

Action: Verify a valid resource type was supplied and contact Oracle support.

Level: 1

Type: ERROR

Impact: Security

OSB-386028: Expected resource key: {0}

Cause: The resource identifier supplied does not contain the expected key.

Action: Specify a valid resource identifier.

Level: 1

Type: ERROR

Impact: Security

OSB-386029: Unknown resource key: {0}

Cause: The resource key supplied in the resource data is unknown.

Action: Specify only resource keys valid for a specific resource type.

Level: 1

Type: ERROR

Impact: Security

OSB-386030: Invalid application name

Cause: The application name parameter was empty or contains invalid values.

Action: Specify a valid application name.

Level: 1

Type: ERROR

Impact: Security

OSB-386031: Invalid component name

Cause: The component name parameter was empty or contains invalid values.

Action: Specify a valid component name.

Level: 1

Type: ERROR

Impact: Security

OSB-386032: Illegal application search name

Cause: The application name was not a legal search string.

Action: Specify a valid application name search string.

Level: 1

Type: ERROR

Impact: Security

OSB-386033: Illegal component search name

Cause: The component name was not a legal search string.

Action: Specify a valid component name search string.

Level: 1

Type: ERROR

Impact: Security

OSB-386034: No component type

Cause: The component type parameter is empty.

Action: Specify a valid component type of EJB, WebApp, Connector or WebService.

Level: 1

Type: ERROR

Impact: Security

OSB-386035: Invalid component type: "{0}"

Cause: The component type parameter specified is not valid.

Action: Specify a valid component type of EJB, WebApp, Connector or WebService.

Level: 1

Type: ERROR

Impact: Security

OSB-386036: Empty array value found

Cause: An empty string was supplied for an array element of the resource key.

Action: Specify a valid string.

Level: 1

Type: ERROR

Impact: Security

OSB-386037: Unexpected resource identifier data: "{0}"

Cause: The resource identifier supplied contains unexpected data.

Action: Specify a valid resource identifier.

Level: 1

Type: ERROR

Impact: Security

OSB-386038: Unexpected resource key array value: "{0}"

Cause: An unexpected value was supplied for a resource key array.

Action: Specify a valid resource identifier.

Level: 1

Type: ERROR

Impact: Security

OSB-386039: Empty {0} resource {1} string

Cause: An empty string was supplied for an element of the resource.

Action: Specify a valid string.

Level: 1

Type: ERROR

Impact: Security

OSB-386040: Empty {0} resource {1} array string

Cause: An empty string was supplied for an array element of the resource.

Action: Specify a valid string.

Level: 1

Type: ERROR

Impact: Security

OSB-386041: key-pair binding with alias "{1}" and purpose "{2}", but there is no such key-pair binding in the PKI Credential Mapper Provider in your security realm

Cause: In older release of ALSB (2.0 and 2.1), ALSB did not include the password to service key provider key-pair credentials in exported configuration jar files. When such a service key provider is later imported into subsequent releases, OSB expects the key-pair binding to already be present in the PKI Credential Mapper Provider. To do that, you would export the PKI Credential Mapper Provider data from your previous domain and import it into your new domain. NOTE: It is recommended that you instead re-configure this service key provider credentials, that way OSB will keep an encrypted copy of the key-pair's password and this error will not happen again

Action: Either import the PKI Credential Mapper provider data or reconfigure the service key provider's credentials in the OSB console

Level: 1

Type: ERROR

Impact: Security

OSB-386042: Mapped service account "{0}" is invalid: the remote-user table is invalid, there are multiple entries with username "{1}"

Cause: The remote user table in a mapped service account cannot have multiple entries with the same username

Action: Edit the mapped service account and remove the duplicate entry

Level: 1

Type: ERROR

Impact: Security

OSB-386043: Service Key Provider "{0}" has a WSS X.509 Token credential and a Digital Signature credential, and they refer to different keys. WSS X.509 credentials have been deprecated. You must remove the WSS X.509 credential.

Cause: WSS X.509 credentials have been deprecated. You must remove the WSS X.509 credential.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386100: Authentication failed

Cause: Authentication failed

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386101: Missing authentication token

Cause: Missing authentication token

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386102: Message-level authorization denied

Cause: Message-level authorization denied

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386200: General web service security error

Cause: General web service security error

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386201: A web service security fault occurred

Cause: A web service security fault occurred

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386400: General outbound web service security error

Cause: General outbound web service security error

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386401: Failed to convert outbound message to SOAP

Cause: Failed to convert outbound message to SOAP

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386402: Cannot determine the outbound operation

Cause: Cannot determine the outbound operation

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386415: Could not enforce access control policy: {0}

Cause: Failed to enforce access control policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386417: Could not get the Authorization Manager

Cause: Failed to get the Authorization Manager

Action: Contact Oracle Support Services

Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-386420: A web service security error ocurred while producing security header

Cause: A web service security error ocurred while producing security header

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386440: A web service security error occurred while processing the security header

Cause: A web service security error occurred while processing the security header

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386460: Web service security policy validation error

Cause: Web service security policy validation error

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386800: Could not find Authorization Provider ${0}

Cause: Failed to get the Authorization Provider.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386801: An error occurred while activating access control changes for proxy "{0}".

Cause: Error while activating the access control changes.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386802: An error occurred while removing access control policy from provider "{0}" with resource id "{1}".

Cause: Error removing access control policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386803: An error occurred while removing access control policy from provider "{1}" for service "{0}" at scope "{2}".

Cause: Error removing access control policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386804: An error occurred while finding access control policy from provider "{0}" with resource id "{1}".

Cause: Error finding access control policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386805: An error occurred while finding access control policy from provider {1} for service {0} at scope {2}.

Cause: Error finding access control policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386806: An error occurred while adding access control policy to provider "{0}" with resource id "{1}".

Cause: Error adding access control policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386807: An error occurred while adding access control policy to provider "{1}" for service "{0}" at scope "{2}".

Cause: Error adding access control policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386808: An error occurred while setting access control policy expression on provider "{0}" with resource id "{1}".

Cause: Error setting access control policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386809: An error occurred while setting access control policy expression on provider "{1}" for service "{0}" at scope "{2}".

Cause: Error setting access control policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386810: Policy for resource id "{1}" already exists in provider "{0}".

Cause: Duplicate policy found.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386820: Argument "{0}" has an invalid value "{1}".

Cause: Invalid argument specified.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386830: Invalid access control policy expression "{3}" for service "{0}" at "{1}" level for provider "{2}".

Cause: Invalid access control policy expression specified.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386831: Multiple policies found for provider "{2}" for service "{0}" at scope "{1}".

Cause: Update the service to have only one policy from a provider at the given scope.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386832: Access control policy found for invalid operation "{1}" for service "{0}".

Cause: Access control policy applied on an invalid operation.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386833: Multiple policy entry found for same operation "{1}" for service "{0}".

Cause: Multiple policy entry found for same operation for a service.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386834: Access control policy found for non-existing provider "{1}" in service "{0}".

Cause: Access control policy found for non-existing provider.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386835: Access control policy found for non-existing operation "{1}" in service "{0}".

Cause: Access control policy found for non-existing operation.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386836: Unnecessary proxy wide message access control policy found for service "{0}".

Cause: Hint: The service is neither an active security intermediary nor has custom authentication enabled.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386837: Unnecessary operation specific message access control policy found for operation "{1}" on service "{0}".

Cause: Hint: The service is not WSDL based.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386838: Unnecessary operation specific message access control policy found for service "{0}".

Cause: Hint: The service is neither an active security intermediary nor has custom authentication enabled.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386839: Message level access control policy found for non-existing operation "{1}" on service "{0}".

Cause: Message level access control policy found for non-existing operation.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386840: Invalid authorization provider "{2}" found in service "{0}" at "{1}".

Cause: Invalid authorization provider specified.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-386841: Authorization provider "{0}" does not exist.

Cause: Authorization provider does not exist. Please check the provider.

Action: Authorization provider does not exist. Please check the provider.

Level: 1

Type: ERROR

Impact: Security

OSB-387000: Failed to initialize Authorization Helper

Cause: Failed to initialize Authorization Helper

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387001: No Policy Editor available

Cause: No Policy Editor available

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387004: Policy deployment for resource {0} failed: {1}

Cause: Error occured during policy deployment.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387008: Failed to get WssPolicyCtx from service {0}

Cause: Failed to get WssPolicyCtx.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387009: Failed to convert message context to SOAPMessage

Cause: Failed to convert message context to SOAPMessage.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387010: Failed to store new SOAPMessage in router's message context

Cause: Failed to store new SOAPMessage in router's message context.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387011: Failed to get the effective request policy for operation {1} for service {0}

Cause: Check the policies attached.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387012: Failed to get the effective response policy for operation {1} for service {0}

Cause: Check the policies attached.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387013: Failed to get the endpoint URL for service {0}

Cause: Failed to get the endpoint URL for service.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387014: The request could not be mapped to one of the operations exposed by the service

Cause: Failed to map request to operation on the service.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387015: Failed to get the outbound operation name from the router's message context

Cause: Failed to get the outbound operation name from the router's message context

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387016: There is no target operation set on the outbound endpoint, the operation must be set in order to fetch the appropriate policy, set the operation in the message context

Cause: There is no target operation set on the outbound endpoint, the operation must be set in order to fetch the appropriate policy, set the operation in the message context

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387018: Unexpected ProviderNotFoundException while deleting user/password credentials for service account {0}

Cause: Unexpected Error while deleting credentials in service account

Action: Contact Oracle Support Services

Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387019: Unexpected ProviderNotFoundException while deleting PKI credentials for service key provider {0}

Cause: Exception while deleting PKI credentials for service key provider.

Action: Contact Oracle Support Services

Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387022: An error occurred during web service security inbound request processing [error-code: {0}, message-id: {1}, proxy: {2}, operation: {3}]--- Error message:{4}

Cause: Check the stacktrace for the error.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387023: An error occurred during web service security inbound response processing [error-code: {0}, message-id: {1}, proxy: {2}, operation: {3}]--- Error message:{4}

Cause: Check the stacktrace for the error.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387024: An error occurred during web service security outbound request processing [error-code: {0}, message-id: {1}, service: {2}, operation: {3}]--- Error message:{4}

Cause: Check the stacktrace for the error.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387025: An error occurred during web service security outbound response processing [error-code: {0}, message-id: {1}, service: {2}, operation: {3}]--- Error message:{4}

Cause: Check the stacktrace for the error.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387026: An internal web service security error occurred [error-code: {0}, message-id: {1}, service: {2}, operation: {3}]--- Error message:{4}

Cause: Check the stacktrace for the error.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387028: Message-level access control policy denies access to proxy "{0}", operation "{1}", message-id: {2}, subject: {3}.

Cause: Message-level access control policy denied.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387029: An error happened while incrementing monitoring counter "{0}" [message-id: {1}, service: {2}, operation: {3}]

Cause: Check the stacktrace to find the cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387030: Cannot read SerializedMS.dat: an IOException was thrown while reading data from {0}.

Cause: Cannot read SerializedMS.dat: an IOException thrown while reading the data.

Action: Contact Oracle Support Services

Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-387031: SerializedMS.dat error: version mismatch, path: {0}. The version of the SerializedMS.dat file is not the supported version. Got version {1}, expected version {2}.

Cause: Verify that the SerializedMS.dat file has not been corrupted.

Action: Contact Oracle Support Services

Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-387032: Error opening SerializedMS.dat: {0}. A FileNotFoundException was thrown while opening the input stream.

Cause: Verify that the SerializedMS.dat file exists and is accessible. Read the exception text for more information on diagnosing the problem.

Action: Contact Oracle Support Services

Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-387033: Error closing SerializedMS.dat: {0}. An IOException was thrown on the close of the input stream while reading the SerializedMS.dat file. Verify that the SerializedMS.dat file is valid. Read the exception text for more information on diagnosing the problem.

Cause: An IOException was thrown on the close of the input stream while reading the SerializedMS.dat file. Verify that the SerializedMS.dat file is valid. Read the exception text for more information on diagnosing the problem.

Action: Contact Oracle Support Services

Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-387034: Could not create temporary file for {0} , .new, {1}

Cause: When creating a temporary file, an IOException was thrown by the File.createTempFile method.

Action: Verify the filename and directory. Read the exception text for more information on diagnosing the problem.

Level: 1

Type: ERROR

Impact: Security

OSB-387035: Could not create temporary file for {0}, .old, {1}

Cause: When creating a temporary file, an IOException was thrown by the File.createTempFile method and the temp file could not be created.

Action: Verify the filename and directory. Read the exception text for more information on diagnosing the problem.

Level: 1

Type: ERROR

Impact: Security

OSB-387036: Could not clear temporary file {0}

Cause: The temporary file could not be deleted.

Action: Verify that the file can be deleted and is not locked by some other process.

Level: 1

Type: ERROR

Impact: Security

OSB-387037: Could not rename {0} to {1}

Cause: The temporary file could not be renamed.

Action: Verify that the file can be renamed and is not locked by some other process.

Level: 1

Type: ERROR

Impact: Security

OSB-387038: Could not delete {0}

Cause: The temporary file could not be deleted.

Action: Verify that the file can be deleted and is not locked by some other process.

Level: 1

Type: ERROR

Impact: Security

OSB-387039: Error creating {0}

Cause: When writing a file using a FileOutputStream, a FileNotFound exception was thrown. Either the file does not exist, the file is a directory rather than a regular file, or the file cannot be opened for reading.

Action: Verify the filename. Read the exception text for more information on diagnosing the problem.

Level: 1

Type: ERROR

Impact: Security

OSB-387040: Error writing to file {0}

Cause: When writing a file using a FileOutputStream, an IOException was thrown.

Action: Read the exception text for more information on diagnosing the problem.

Level: 1

Type: ERROR

Impact: Security

OSB-387041: There are more than one user password credential mapper providers configured in your security realm. Oracle Service Bus supports at most one user password credential mapper. OSB service account management will be disabled. Review your realm configuration and make sure there is at most one provider.

Cause: There are more than one user password credential mapper providers configured in your security realm. Oracle Service Bus supports at most one user password credential mapper. OSB service account management will be disabled. Review your realm configuration and make sure there is at most one provider.

Action: Contact Oracle Support Services

Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387042: There is no user password credential mapper provider configured in your security realm. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need OSB service account support.

Cause: There is no user password credential mapper provider configured in your security realm. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need OSB service account support.

Action: Contact Oracle Support Services

Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387043: The user password credential mapper provider configured in your security realm does not implement UserPasswordCredentialMapEditorMBean. This is a read-only provider. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider that supports writes if you need OSB service account support.

Cause: The user password credential mapper provider configured in your security realm does not implement UserPasswordCredentialMapEditorMBean. This is a read-only provider. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider that supports writes if you need OSB service account support.

Action: Contact Oracle Support Services

Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387044: Invalid service account {0}: the service account does not have a name

Cause: Specify a valid name to the Service Account.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387045: Invalid service account {0}: the service account does not have a type

Cause: Create a service account of valid type

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387046: Invalid service account type: {0}

Cause: Create a service account of valid type

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387047: Invalid static service account {0}: the service account does not have a username/password

Cause: Static service account should have a username/password

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387048: Invalid static service account {0}: the username is null

Cause: Static service account should have a valid username.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387049: Invalid static service account {0}: the username is invalid

Cause: Static service account should have a valid username.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387050: Invalid static service account {0}: the password is null

Cause: Static service account should have a valid password.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387051: Invalid static service account {0}: the password is invalid

Cause: Static service account should have a valid password.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387052: Invalid mapper service account {0}: the service account does not have any user mapping entries or an anonymous mapping

Cause: Mapper service account should have valid user mapping entries or an anonymous mapping

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387053: Invalid mapper service account {0}: local username in user mapping is null

Cause: Mapper service account should have a valid local username in user mapping

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387054: Invalid mapper service account {0}: local username is invalid

Cause: Mapper service account should have a valid local username in user mapping

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387055: Invalid mapper service account {0}: the map has an entry with a null remote username/password

Cause: Mapper service account should have a valid remote username/password

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387056: Invalid mapper service account {0}: the map has an entry with a null remote username

Cause: Mapper service account should have a valid remote username

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387057: Invalid mapper service account {0}: the map has an entry with an invalid remote username

Cause: Mapper service account should have a valid remote username

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387058: Invalid mapper service account {0}: the map has an entry with a null remote password

Cause: Mapper service account should have a valid remote password

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387059: Invalid mapper service account {0}: the map has an entry with an invalid remote password

Cause: Mapper service account should have a valid remote password

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387060: Invalid mapper service account {0}: the service account has an anonymous mapping but the remote username on the anonymous mapping is null

Cause: Mapper service account should have a valid remote username

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387061: Invalid mapper service account {0}: the service account has an anonymous mapping but the remote username on the anonymous mapping is invalid

Cause: Mapper service account should have a valid remote username

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387062: Invalid mapper service account {0}: the service account has an anonymous mapping but the remote password on the anonymous mapping is null

Cause: Mapper service account should have a valid remote password

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387063: Invalid mapper service account {0}: the service account has an anonymous mapping but the remote password on the anonymous mapping is invalid

Cause: Mapper service account should have a valid remote password

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387066: An error occurred while activating changes for service account {0}.

Cause: This is an unexpected error. Check the logs for more details.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387067: There are more than one PKI credential mapper providers configured in your security realm. Oracle Service Bus supports at most one PKI credential mapper. OSB service key provider management will be disabled. Review your realm configuration and make sure there is at most one PKI credential mapper provider.

Cause: There are more than one PKI credential mapper providers configured in your security realm. Oracle Service Bus supports at most one PKI credential mapper. OSB service key provider management will be disabled. Review your realm configuration and make sure there is at most one PKI credential mapper provider.

Action: Contact Oracle Support Services

Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387069: The PKI credential mapper provider configured in your security realm does not implement PKICredentialMapEditorMBean. This is a read-only provider. Oracle Service Bus service key provider management will be disabled. Configure a PKI credential mapper provider that supports writes if you need OSB service provider support. This is typically the case if you have OSB proxies with web service security enabled or outbound 2-way SSL connections.

Cause: The PKI credential mapper provider configured in your security realm does not implement PKICredentialMapEditorMBean. This is a read-only provider. Oracle Service Bus service key provider management will be disabled. Configure a PKI credential mapper provider that supports writes if you need OSB service provider support. This is typically the case if you have OSB proxies with web service security enabled or outbound 2-way SSL connections.

Action: Contact Oracle Support Services

Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387072: An error occurred while persisting the changes for service key provider {0} to credential mapping provider {1}. The PKI credentials associated with service providers are now in an inconsistent state. This requires immediate attention. Error: {3}

Cause: See the stacktrace for additional information.

Action: Contact your Oracle representative.

Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-387073: Invalid service key provider {0}: missing key-alias for {1} key

Cause: Service key provider should have valid key-alias for all keys.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387074: Invalid service key provider {0}: invalid key-alias for {1} key

Cause: Service key provider should have valid key-alias for all keys.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387075: Invalid service key provider {0}: missing key-password for {1} key

Cause: Service key provider should have valid key-password for all keys.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387076: Invalid service key provider {0}: invalid key-password for {1} key

Cause: Service key provider should have valid key-password for all keys.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387077: Invalid 21 compatibility resource id in service key provider {0} for {1} key: {2}

Cause: Invalid 21 compatibility resource id in service key provider

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387078: Failed to bind key-pair credential for service key provider {0} and purpose {1}: {2}

Cause: Check the logs to diagnose the error

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387079: Failed to bind key-pair credential for service key provider {0} for digital signature purposes: the certificate does not support digital signatures. Key-alias: {1}

Cause: Specify valid certificate which supports the digital signature.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387080: Failed to bind key-pair credential for service key provider {0} for encryption purposes: the certificate does not support encryption. Key-alias: {1}

Cause: Specify valid certificate which supports the digital encryption.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387081: Error in service key provider "{0}": could not read a certificate under keystore alias "{1}" for purpose "{2}"

Cause: Check the stacktrace to diagnose the error

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387082: Proxy service access denied (proxy: {0}, subject: {1})

Cause: Check the accenss control policy for the proxy service

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387095: [Policy Migration] [proxy service: {0}] [authorization provider: {1}] The 2.1 policy cannot be migrated because it makes use of policy predicates which are specific to URLResource. A deny-all policy will be bound to the proxy. You must re-configure this policy in the console.

Cause: The 2.1 policy cannot be migrated because it makes use of policy predicates which are specific to URLResource. A deny-all policy will be bound to the proxy. You must re-configure this policy in the console.

Action: Contact Oracle Support Services

Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387096: Oracle Service Bus could not determine if the default ALSBProxyServiceResource policy is present or not because some authorization providers do not implement PolicyReaderMBean. OSB could not deploy the policy because neither EntitleNet provider nor XACML provider is present. If the policy is indeed missing, the administrator must create it.

Cause: Oracle Service Bus could not determine if the default ALSBProxyServiceResource policy is present or not because some authorization providers do not implement PolicyReaderMBean. OSB could not deploy the policy because neither EntitleNet provider nor XACML provider is present. If the policy is indeed missing, the administrator must create it.

Action: Contact Oracle Support Services

Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387097: Oracle Service Bus has determined the default ALSBProxyServiceResource policy is missing. OSB could not deploy the policy because neither EntitleNet provider nor XACML provider is present. Access to all OSB proxy services will be denied. The administrator must create the policy using the provider tools.

Cause: Oracle Service Bus has determined the default ALSBProxyServiceResource policy is missing. OSB could not deploy the policy because neither EntitleNet provider nor XACML provider is present. Access to all OSB proxy services will be denied. The administrator must create the policy using the provider tools.

Action: Contact Oracle Support Services

Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-387099: Service Key Provider "{0}" has a WSS X.509 Token credential. WSS X.509 credentials have been deprecated. You must configure a Digital Signature credential instead.

Cause: WSS X.509 credentials have been deprecated. You must configure a Digital Signature credential instead.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387100: Service "{0}" is configured as No Policies, but policies have been found in the service definition.

Cause: Service is configured as No Policies, but policies have been found in the service definition.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387102: Exception in {0}, {1}

Cause: A general runtime error has occured during OSB's OWSM support initialization

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387105: Exception in {0}, continuing, {1}

Cause: This is an informational message that is logged during the OSB's OWSM support initialization process when a non-fatal exception occurs

Action: No action is necessary

Level: 1

Type: ERROR

Impact: Security

OSB-387176: OWSM Policies can't be bounded at the Operation level

Cause: Attaching OWSM Policies at the Operation Level is not supported by OWSM. Policies can be attached only at the service level currently.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387177: OWSM Policy {0} is not supported.

Cause: This Policy is not supported. Refer OSB documentation on list of supported policies.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387178: An error occurred while computing the web service policy for service {0}: {1}

Cause: An error occurred while computing the web service policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387179: OWSM Policies are not supported on WSRM Transport

Cause: OWSM Policies are not supported on WSRM Transport

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387180: OSB does not support attaching OWSM MTOM/no-MTOM Policy on Proxy/Business Service. Please delete these OWSM Policies. For MTOM support in OSB enable MTOM configuration on the Pipeline/Business Service.

Cause: OSB does not support attaching OWSM MTOM/no-MTOM Policy on Proxy/Business Service. Please delete these OWSM Policies. For MTOM support in OSB enable MTOM configuration on the Pipeline/Business Service.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387181: This service can not have both WebLogic Server 9.X-style security policies and owsm policies

Cause: Configure the service's ws-policy. Make sure it does not have any WebLogic Server 9.X-style security policy along with the OWSM policies.

Action: Configure the service's ws-policy. Make sure it does not have any WebLogic Server 9.X-style security policy along with the OWSM policies.

Level: 1

Type: ERROR

Impact: Security

OSB-387182: This service can not have both OWSM security policies and a service account

Cause: Service account can not be configured on a service attached with OWSM policies.

Action: Configure the service's ws-policy. Make sure it does not have any WebLogic Server 9.X-style security policy along with the OWSM policies.

Level: 1

Type: ERROR

Impact: Security

OSB-387187: OWSM Policy Support is not available in this environment. Upgrade your domain if you need OWSM Policy support. Please see documentation on how to upgrade your domain.

Cause: OWSM Policy Support is not available in this environment. Upgrade your domain if you need OWSM Policy support. Please see documentation on how to upgrade your domain.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387189: OWSM Policy ''{0}'' is not allowed on ''{1}'' transport.

Cause: Refer OSB documentation for supported policies on the transport.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387190: OWSM Policy ''{0}'' is not allowed since transport authentication is set to ''None''. If you are trying to attach an HTTP Token Policy make sure the transport authentication is set to Basic Authentication.

Cause: OWSM transport policies attached have to match with the transport configuration for the service. If you are trying to attach an HTTP Token Policy make sure the transport authentication is set to Basic Authentication.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387191: OWSM Policy ''{0}'' is not allowed since transport authentication is set to ''{1}''. Authentication method on the policy conflicts with the configuration on the transport.

Cause: Update the policies to match the transport configuration of the service.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387194: OWSM Policy ''{1}'' is not allowed since transport authentication is set to ''{0}''. If you are trying to attach an HTTP Token Policy make sure that the authentication on transport configuration is set to ''None''. You can either set the authentication mechanism directly on the transport configuration page or attach OWSM HTTP Token Policy.

Cause: If you are trying to attach an HTTP Token Policy make sure that the authentication on transport configuration is set to ''None''. You can either set the authentication mechanism directly on the transport configuration page or attach OWSM HTTP Token Policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387195: OWSM Policy ''{0}'' contains unsupported authentication method ''{1}''. Only ''Basic'' , ''SPNEGO'' and ''HTTP SAML 2.0 Bearer Token'' authentications are supported with OWSM policy.

Cause: Edit OWSM policy in Enterprise Manager and change the authentication mechanism to ''Basic'' , ''SPNEGO'' or ''HTTP SAML 2.0 Bearer Token''. For any other authentication method, directly configure on the transport and do not attach any OWSM HTTP Token policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387196: The service has both OWSM Transport Policy ''{0}'' and transport level access controls. This combination is not supported. If OWSM Transport Policy is used, OWSM authorization policy should be used.

Cause: Solution: Either remove OWSM Transport Policy and replace that intent by configuring authentication directly on the transport OR remove transport ACLs from the Security page and replace them with OWSM Authorization Policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387197: The service has OWSM Transport Policy ''{0}'' with transport security enabled but HTTPS is not enabled on this service.

Cause: This combination is not supported. Please enable ''HTTPS Required'' on transport configuration page OR disable transport security on the OWSM policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387198: The service has OWSM Transport Policy ''{0}'' with mutual authentication (TWO WAY SSL) enabled.

Cause: This configuration is not supported. Please disable the mutual authentication on the OWSM policy.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387201: The service has OWSM Transport Policy ''{0}'' with Include Timestamp enabled. This configuration is not supported. Please disable the Include Timestamp attribute on the OWSM policy.

Cause: The service has OWSM Transport Policy with Include Timestamp enabled. This configuration is not supported.

Action: Disable the Include Timestamp attribute for the policy from EM

Level: 1

Type: ERROR

Impact: Security

OSB-387203: The business service does not have a STS configuration policy attached

Cause: (any soap) business service with STS issue token policy does not have STS configuration policy

Action: Attach a STS Configuration policy to the business service

Level: 1

Type: ERROR

Impact: Security

OSB-387204: STS information is missing from the attached WSDL and the business service does not have a STS configuration policy attached

Cause: (soap) business service with STS issue token policy does not have STS information available

Action: Attach a STS Configuration policy to the business service, or attach a WSDL with STS information present

Level: 1

Type: ERROR

Impact: Security

OSB-387207: HTTP proxy/business service can not have both AT(atomic_transaction) and RM(reliable_messaging) policies together.

Cause: HTTP service can not be configured with both AT and RM policies.

Action: Either AT(atomic_transaction) or RM(reliable_messaging) policy but not both can be applied to a HTTP poxy/business services.

Level: 1

Type: ERROR

Impact: Security

OSB-387211: HTTP proxy/business service can not have RM(reliable_messaging_policy) policy.

Cause: HTTP service can not be configured with RM policy.

Action: To enable RM, system property with name com.oracle.osb.disi.rm.enabled must be set with its value as true.

Level: 1

Type: ERROR

Impact: Security

OSB-387212: HTTP proxy/business service with RM(reliable_messaging_policy) policy should also have (reliable_messaging_internal_api_policy) policy.

Cause: HTTP service with incomplete RM policy.

Action: Add (oracle/reliable_messaging_internal_api_policy) policy along with (reliable_messaging_policy) policy.

Level: 1

Type: ERROR

Impact: Security

OSB-387251: Policy ID {0} is not supported.

Cause: This policy is not supported by OSB. Refer to the documentation for list of supported policies.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387252: Multiple policies found for given policy ID {0}.

Cause: Remove the duplicate policies.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387253: Failed to validate OWSM credentials due to the following error: {0}

Cause: This is an informational message that is logged during the OSB's OWSM support' config overrides validation process when a non-fatal exception occurs. Skipping config overrides validation as OSB failed to access the configured Keystore and Credential Store. Refer to OWSM documentation for details on Keystore and Credential Store configuration.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387254: Failed to validate the Override Value "{0}" due to the following error: {1}

Cause: This is an informational message that is logged during the OSB's OWSM support config overrides validation process when a non-fatal exception occurs.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387256: Invalid CSF Key ''{1}'' set for override ''{0}''. This CSF Key does not exist in the Credential Store.

Cause: This is an informational message that is logged during the OSB's OWSM support config overrides validation process when a non-fatal exception occurs.

Action: Update the Credential Store with the required CSF Key.

Level: 1

Type: ERROR

Impact: Security

OSB-387257: Invalid Recepient Alias "{0}" specified.

Cause: This is an informational message that is logged during the OSB's OWSM support config overrides validation process when a non-fatal exception occurs.

Action: Update the keystore with the required certificate.

Level: 1

Type: ERROR

Impact: Security

OSB-387258: Invalid Value {1} specified for {0}. Valid values are {2}.

Cause: Invalid version specified.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387259: Invalid wssp value "{1}" specified for wsp: "{0}". Valid wssp values are: "{2}".

Cause: Invalid combination of wssp and wsp versions specified.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387260: Query parameters "wsp" and "wssp" are not supported for ORAWSDL.

Cause: ORAWSDL does not support "wsp" and "wssp" parameters.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Security

OSB-387301: Unexpected error happened in the JEJB Transport at {0} due to {1}

Cause: An internal error occurred. It is due to either an unrecoverable failure during a configuration update or a runtime error during message processing

Action: If this error happened during a configuration update, check that your JEJB transport services are not corrupted. In case of corrupted configuration, manually clean up the failed services or restart your server. For other errors, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-387302: Could not create connection with proxy service {0} due to {1}

Cause: An error happened while trying to lookup the JEJB Transport proxy service RMI stubs

Action: Verify that your JNDI context host, port and credentials are correct. Also check that protocol used by the JNDI context is supported and enabled. For instance, IIOP/IIOPS protocols are not supported between WebLogic Server, and HTTP/HTTPS protocols requires HTTP tunneling

Level: 1

Type: ERROR

Impact: Other

OSB-387303: Could not invoke proxy service {0} due to {1}

Cause: An Remote Exception happened while trying to invoke the JEJB Transport proxy service via RMI

Action: Check your that network connection, destination server and port are up. Also, check that the remote proxy service still exists

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387304: Could not generate plan {0} due to {1}

Cause: An internal error occurred while creating a proxy services with a custom dispatch policy. The deployment plan for this proxy artifact could not be created

Action: The message body should give you more details about the error. This could be caused by a I/O Exception or because the location of the deployment plan write-protected.

Level: 1

Type: ERROR

Impact: Deployment

OSB-387305: Unsupported payload type {0}

Cause: An internal error occurred during the message processing: the payload associated with the message is not supported by the JEJB Transport

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387306: Method: {0} is not exposed through JEJB inbound service for invocation.

Cause: This method is not exposed by the JEJB proxy service for invocation.

Action: Please check the proxy service configuration.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387307: Method: {0} is not exposed through JEJB business service for invocation.

Cause: This method is not exposed by the JEJB business service for invocation.

Action: Please check the business service configuration.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387308: Corresponding OSB service is in disabled state.

Cause: Corresponding OSB service is in disabled state.

Action: Please enable the corresponding proxy service.

Level: 1

Type: ERROR

Impact: Configuration

OSB-387309: Following Response payload to the inbound JEJB service is not properly formed: {0}

Cause: Response payload to the inbound JEJB service is not properly formed.

Action: Response message should be modeled as the SOAP message with operation name as the sub-elements. Please refer to the generated wsdl for the message structure.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387310: Following Request payload to the outbound JEJB service is not properly formed: {0}

Cause: Request payload to the outbound JEJB service is not properly formed.

Action: Request message should be modeled as the SOAP message with operation name as the sub-elements. Please refer to the generated wsdl for the message structure.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387311: Parameter: {0} with class name: {1} could not be loaded

Cause: Parameter received from the payload could not be loaded.

Action: Please look at the exception message for the reason. Refer to the generated wsdl for the message structure.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387312: No object is registered for ref ''{0}''

Cause: An attempt to look up an object in Java object repository with the specified reference failed. This may have occurred to due a previously executed pipeline action that deleted the object with the corresponding reference.

Action: Check the pipeline message flow configuration to make sure there is no pipeline action that deletes the object with the specified reference that executes prior to this error.

Level: 1

Type: ERROR

Impact: Other

OSB-387313: Colocated call is not supported by JEJB transport provider.

Cause: Colocated call is not supported by JEJB transport provider.

Action: Colocated calls are not supported by JEJB transport provider. Please route the pipeline message to JEJB business service.

Level: 1

Type: ERROR

Impact: Configuration

OSB-387314: JNDI Provider: {0} could not be retrieved due to {1}

Cause: JNDI Provider could not be retrieved due to an unexpected error.

Action: Please look at error message for the reason. If problem persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Configuration

OSB-387315: JNDI Provider: {0} not found

Cause: JNDI Provider does not exists in OSB

Action: Please make sure that a valid JNDI Provider is configured with the given name.

Level: 1

Type: ERROR

Impact: Configuration

OSB-387316: Unexpected error while creating or updating the JEJB Service due to {0}

Cause: Unexpected error while creating or updating the JEJB Service due to {0}

Action: Please look at the error for the actual reason.

Level: 1

Type: ERROR

Impact: Deployment

OSB-387317: Could not find an existing JNDI provider with one of the following URIs: {0}

Cause: Could not find an existing JNDI provider with one of the following URIs: {0}

Action: While importing the JEJB service from UDDI, JEJB Transport Provider looks for existing JNDI provider with the same host and port as mentioned in the access point of the imported service. Make sure that a JNDI provider is already created at the time of importing the service. Please refer to the documentation for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387318: Java object received from the pipeline message with type: {0} cannot be converted to the expected type: {1}

Cause: Java object received from the pipeline message cannot be converted to the expected type.

Action: Please check the pipeline logic. Java object received from the pipeline message cannot be converted to the expected type as defined in the ejb interface.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-390003: Child resource {0} is not associated with a parent resource

Cause: Child resource is not associated with a parent resource

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-390004: Child resource {0} is associated with more than one parent resource

Cause: More than one resource instance contains a reference to a child instance. Instances of resources that are defined as Child types can only be references by instances of resources that are defined as Parent types, through parent-child references. Update references in the parent instances or delete one of the parent instances so that only one has a child reference to the child resource.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-390005: Dangling child reference from {0} to {1}

Cause: Dangling child reference from parent.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-390006: Parent resource {0} has multiple containments of child resource {1}. Containment names: {2}

Cause: A parent resource can reference a child resource only once.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-390013: Execution record for the given task was not found

Cause: An attempt is made to undo a previous change, but the information about the change, is not found. No execution record was found with the task id supplied by the user. The task id may be invalid, or the execution record may have been purged by the admin

Action: Make sure you are using the correct task id.

Level: 1

Type: ERROR

Impact: Data

OSB-390014: Change has already been undone

Cause: An attempt is made to undo a previous change twice.

Action: No action is necessary

Level: 1

Type: ERROR

Impact: Other

OSB-390015: No undo record found for task

Cause: An attempt is made to undo a previous change, but the change cannot be undone. Certain internal changes initiated by the server cannot be undone.

Action: No action is necessary

Level: 1

Type: ERROR

Impact: Data

OSB-390018: Undo cannot be completed because the changes have errors. See log file for details

Cause: Undo cannot be completed because the changes have errors. See log file for details

Action: Inspect the error log, and if there are validation errors in resources, attempt to fix them.

Level: 1

Type: ERROR

Impact: Other

OSB-390019: No exec records for session {0}

Cause: Unexpected error due to a failed session activation

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Session

OSB-390101: Activation of session {0} failed: {1}

Cause: Activation of session failed. The exception should provide more detail.

Action: Inspect the error message and try to fix any validation errors or add systems resources that are missing.

Level: 1

Type: ERROR

Impact: Session

OSB-390103: Failed to discard session {0} after successful activation: {1}

Cause: Failed to discard session after successful activation. The exception should provide more detail.

Action: Retry the discard operation.

Level: 1

Type: ERROR

Impact: Session

OSB-390104: Failed to create WLS change list for activation of session {0}: {1}

Cause: Session activation requires a lock on WLS configuration to perform any deployments that are required by the resources. However the lock could not be obtained Another session activation may be in progress, or another user may have already started a WLS change list and holding the lock.

Action: If another session activation is already in progress, wait until the activation finishes. If another user is holding the lock, contact the user.

Level: 1

Type: ERROR

Impact: Session

OSB-390105: Unable to create WLS change list due to a short term automatic lock obtained by user {0}. The user has no pending changes and the lock will expire in {1} seconds. Please try again after the lock has expired.

Cause: Session activation requires a lock on WLS configuration to perform any deployments that are required by the resources. In this case the lock is obtained automatically by WLS console on behalf of the user. The lock is obtained regardless of any changes, and will expire in a short time.

Action: Wait until the lock expires or the other user explicitly releases the lock, and try again.

Level: 1

Type: ERROR

Impact: Session

OSB-390106: Failed to cancel WLS change list: {0}

Cause: An unexpected error occurred when cancelling WLS changes after a failed session activation

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Session

OSB-390108: Cannot Create or Edit or Activate or Exit session because there are unexpected errors occurred: {0}

Cause: Cannot Create or Edit or Activate or Exit session because there are unexpected errors occurred. The message should provide more detail.

Action: Retry the activation.

Level: 1

Type: ERROR

Impact: Session

OSB-390109: Failed to notify session listener {1} for operation {2} on session {0}

Cause: An unexpected error occured when activating changes.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Session

OSB-390111: Another session operation is in progress. Please retry later.

Cause: Another session operation is in progress. Please retry later.

Action: Retry the session activation after the other activation finishes

Level: 1

Type: ERROR

Impact: Session

OSB-390112: No session was specified.

Cause: Certain configuration APIs work only in a session, but no session name is passed in the arguments.

Action: Make sure you provide the session name.

Level: 1

Type: ERROR

Impact: Session

OSB-390113: Resource {0} was not modified in session {1}, therefore cannot sync to the core data.

Cause: An attempt is made to sync to the core changes for a resource that has not been modified in a session. If a resource is modified both in a session, and in the core (via the activation of another session), two versions of the resource conflict. The user can either choose to overwrite core changes simply by activating the session, or sync to the core changes, effectively discarding his own changes.

Action: Make sure you invoke sync operation on a resource that is modified in the session.

Level: 1

Type: ERROR

Impact: Session

OSB-390114: Deployed configuration state has changed while creating a session. Please try creating the session again.

Cause: Deployed configuration state has changed while creating a session. Please try creating the session again.

Action: Retry session creation.

Level: 1

Type: ERROR

Impact: Deployment

OSB-390115: Failed to save WLS changes for session {0}

Cause: WLS changes that are made in response to a session activation has failed

Action: Inspect the error messages from WLS and consult WLS documentation

Level: 1

Type: ERROR

Impact: Deployment

OSB-390116: Failed to release WLS Edit session lock: {0}

Cause: Failed to release WLS Edit session lock. The exception should provide more detail.

Action: No action is necessary

Level: 1

Type: ERROR

Impact: Session

OSB-390117: Failed to instantiate core: {0}

Cause: Unexpected error

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Deployment

OSB-390118: Failed to instantiate session: {0}

Cause: Failed to instantiate session. The exception should provide more detail.

Action: Retry session creation

Level: 1

Type: ERROR

Impact: Session

OSB-390119: Failed to set session description: {0}

Cause: Failed to set session description. The exception should provide more detail.

Action: Make sure you provided the correct session name

Level: 1

Type: ERROR

Impact: Session

OSB-390120: Failed to notify session {0} of core changes: {1}

Cause: When a session is activated, the changes are propagated to other sessions, causing them to absorb the changes and revalidate their own content if necessary. An unexpected error occured while the changes are propagated.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Session

OSB-390121: Session {0} already exists

Cause: You are attempting to create a session that already exists.

Action: When creating a session programmatically, first check if a session with the same name exist. If so you can choose to use it or discard it. When using the console, make sure you are now using a stale view of the configuration by refreshing the page.

Level: 1

Type: ERROR

Impact: Session

OSB-390122: Cannot create session on a non-admin server

Cause: A programmatic attempt is made to create a session on a server other than the admin.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Session

OSB-390123: {0} is an invalid session name

Cause: Session names can contain java identifier characters, '-' or '.'.

Action: Use a session name that contains only the legal character, namely, java identifier characters, '-' or '.'

Level: 1

Type: ERROR

Impact: Session

OSB-390124: Session {0} cannot be discarded because it is being activated

Cause: An attempt is made to discard a session that is in the process of being activated

Action: If the activation is initiated accidentally, wait for the activation to finish successfully and undo the session activation.

Level: 1

Type: ERROR

Impact: Session

OSB-390125: Session {0} was not found

Cause: The session was not found.

Action: Make sure the correct session name is used.

Level: 1

Type: ERROR

Impact: Session

OSB-390206: Rollback failed due to errors

Cause: Rollback failed due to errors.

Action: Make sure you have the correct file permissions, or that you have enough space in file system

Level: 1

Type: ERROR

Impact: Other

OSB-390208: Commit failed due to errors

Cause: Commit failed due to errors

Action: Make sure you have the correct file permissions, or that you have enough space in file system

Level: 1

Type: ERROR

Impact: Other

OSB-390209: Failed to write to transaction file {0}

Cause: Failed to write to transaction file. The exception should provide more detail.

Action: Make sure you have the correct file permissions, or that you have enough space in file system

Level: 24

Type: INCIDENT_ERROR

Impact: Files

OSB-390210: Undo failed

Cause: Undo failed. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-390212: Cannot enlist transactional resource {0} when transaction is in {1} state

Cause: Cannot enlist transactional resource when transaction is in the given state.

Action: Retry the operation that caused this error

Level: 1

Type: ERROR

Impact: Other

OSB-390213: Cannot write transactional resource {0} when transaction is in {1} state

Cause: Cannot write transactional resource when transaction is in the given state.

Action: Retry the operation that caused this error

Level: 1

Type: ERROR

Impact: Other

OSB-390214: No transaction exists

Cause: No transaction exists.

Action: Retry the operation that caused this error

Level: 1

Type: ERROR

Impact: Other

OSB-390215: No file was found

Cause: Internal error

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Files

OSB-390216: Attempting to read from a file that is marked for deletion, file: {0}

Cause: Internal error

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Files

OSB-390300: Startup recoveryFailed

Cause: An attempt from a managed server to synchronize configuration with the admin server has failed.

Action: Inspect the errors and consult WLS documentation.

Level: 1

Type: ERROR

Impact: Disaster Recovery

OSB-390301: Failed to commit deployment

Cause: Failed to commit deployment. The exception should give more detail.

Action: Retry the deployment

Level: 1

Type: ERROR

Impact: Deployment

OSB-390302: Failed to cancel deployment

Cause: Internal error

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Deployment

OSB-390303: Failed to prepare deployment

Cause: Session activation has failed in its prepare phase

Action: Inspect the errors and consult the documentation

Level: 1

Type: ERROR

Impact: Deployment

OSB-390501: No configuration has been uploaded or previously uploaded jar file has already been imported

Cause: An attempt is made to import an uploaded jar twice. An uploaded jar file is deleted from the internal staging area immediately after an import

Action: When importing the same jar twice, make sure you upload it for each time you want to import it

Level: 1

Type: ERROR

Impact: Data

OSB-390504: Invalid jar file

Cause: The jar file that is being imported is not a jar file that was previously exported.

Action: Make sure you are using a jar file that was previously exported. Check if the jar file is meant to be using for bulk import, and if so, use bulk import feature

Level: 1

Type: ERROR

Impact: Data

OSB-390505: The jar that is being imported is an unsupported version of the product. The version was {0}. Supported versions are: {1}

Cause: The jar that is being imported was created using a version of the product that is no longer supported.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-390506: Invalid actions defined for the following environment values: {0}

Cause: Invalid actions have been specified for some environment values.

Action: Only specify valid action for environment values.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394000: Exception on {0}, {1}

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-394003: Failed to send alert to Alert Destination {2}. Resource: {0}. Alert Rule Name: {1}.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-394004: Failed to invoke action {3} that is part of alert destination {2}. Resource: {0}. Alert Rule Name: {1}.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-394005: Failed to send alert to reporting data set. Resource: {0}. Alert Rule Name: {1}. Alert Id: {2}.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-394006: Failed to generate SNMP trap. Resource: {0}. Alert Rule Name: {1}. Alert Id: {2}.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-394007: Failed to store alert in the alert log. Resource: {0}. Alert Rule Name: {1}. Alert Id: {2}.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-394009: Failed to evaluate rules

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-394030: Failed to shutdown SLA Alert Manager.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-394031: Failed to shutdown Pipeline Alert Manager.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-394032: Failed to shutdown Alert Log Manager.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-394033: Failed to unbind AlertLogger.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-394034: Failed while invoking command.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-394500: Error encountered while importing resource: {0}.

Cause: Error occured while importing resource from UDDI. Registry may be down or not accessible.

Action: Please check if the registry is running and try again.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394501: Error encountered while querying for businesses: {0}.

Cause: Error while querying the business entities in registry.

Action: Check if the registry is running and if you have permission to query the business entity.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394503: Error getting UDDI inquiry port : {0}.

Cause: Error while getting the inquiry port. Please check the Inquiry URL entered.

Action: Please check the Inquiry URL entered.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394505: Failed to connect to the UDDI registry.

Cause: Registry may be down or bad inquiry URL provided.

Action: Please verify if the registry is running and accessible. Ensure that the correct inquiry URI is provided.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394506: Error encountered while querying for business services: {0}.

Cause: Some error occured on UDDI registry while querying for the Business Service.

Action: Please check the error logs at UDDI registry.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394507: The registry name contains characters that are not allowed.

Cause: The registry name contains characters that are not allowed.

Action: Please remove the special characters from the registry name.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394510: {0} could not be imported. Please verify if the URI is available

Cause: Registry may be down or not accessible.

Action: Please verify the registry is accessible.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394511: Validation Exception occured on service creation

Cause: Valid failed.

Action: Check the conflicts in Change Center.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394512: User exception while importing repository

Cause: Internal error.

Action: Contact Oracle support.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394513: Repository ID {0} not present : {1}

Cause: Internal Error

Action: Contact Oracle support.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394517: Error getting xml value from InstanceParms : {0}

Cause: Instance Params as received from UDDI gave error while converting to XML.

Action: Verify the Instance params as present in UDDI registry.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394520: Error in AutoImport: {0}

Cause: An error occurred during AutoImport. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-394521: The Publish URL must be specified in order to publish tModels

Cause: Publish URL is not specified for the registry.

Action: Specify the Publish URL.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394522: The Security URL must be specified in order to publish tModels

Cause: Security URL not specified for the registry.

Action: Specify the Security URL.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394525: Error in AutoPublish: {0}

Cause: An error occurred during AutoPublish. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-394528: Rest Service Wsdl could not be imported. Please verify if the URI is available

Cause: Registry may be down or not accessible.

Action: Please verify the registry is accessible.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394550: UDDI Error- Message is : {0}

Cause: UDDI Error occurred. The exception message should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-394551: UDDI Error- Message is : {0}. Exception is : {1}

Cause: UDDI Error occurred. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-394552: An error was encountered while publishing this service : {0}.

Cause: Error while publishing the services or tModels.

Action: Please check if the registry running and if services and tModels follow the UDDI specification.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394553: Failed to connect to the specified publish URL.

Cause: Registry not accessible or bad publish URL specified.

Action: Please ensure that the registry is running and accessible. Verify the publish URL specified for the registry.

Level: 1

Type: ERROR

Impact: Configuration

OSB-394554: Please ensure that the URLs specified for the registry are correct.

Cause: Wrong Publish or Security URL specified.

Action: Please verify whether the Publish and Security URLs are correct and accessible.

Level: 1

Type: ERROR

Impact: Configuration

OSB-395000: Exception in {0}, {1}

Cause: A general runtime error has occured during OSB initialization

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-395005: Exception in {0}, continuing, {1}

Cause: This is an informational message that is logged during the OSB initialization process when a non-fatal exception occurs

Action: No action is necessary

Level: 1

Type: ERROR

Impact: Process

OSB-395007: The OSB debugger failed during initialization: {0}

Cause: A general runtime error has occured during initialization of OSB debugger.

Action: Verify the port defined for the OSB debugger is not already in use by another application or component. Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-395100: The TokenIterator does not correspond to a XmlObject value

Cause: One of the actions has attempted to treat the result of XQuery expression as XML, whereas the actual return value was not XML

Action: Please check the configuration to make sure that the context in which the XQuery expression is used is consistent with the actual return value

Level: 1

Type: ERROR

Impact: Data

OSB-395101: prolog declarations are not allowed for xquery snippets

Cause: The inline XQuery expression has prolog declarations, such as ''declare namespace'' statements. This is not allowed in inline XQuery expressions

Action: Please check the text of inline expression for prolog declarations. If those are really necessary, then register a XQuery resource and use it instead of an inline expression in your action.

Level: 1

Type: ERROR

Impact: Configuration

OSB-395102: The given value is not of a supported type: {0}

Cause: One of the actions has passed an expression to XQuery evaluation engine that is not of recognized type

Action: Please check the configuration of the action to make sure the text of the expression is properly configured and has semantic meaning. Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Data

OSB-395103: Unsupported XQuery Type: {0}

Cause: While evaluating the result of XQuery expression, an unexpected XML token has been found.

Action: Please check the configuration of the action to make sure the text of the expression is properly configured and has semantic meaning. Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Data

OSB-395104: The TokenIterator does not correspond to a single String value

Cause: The result of XQuery expression was expected to be a single String value and was something else.

Action: Please check the configuration of the action to make sure the text of the expression is properly configured and will result in a single String value

Level: 1

Type: ERROR

Impact: Data

OSB-395105: The TokenIterator does not correspond to a single XmlObject value

Cause: The result of XQuery expression was expected to be a single XML object value and was something else.

Action: Please check the configuration of the action to make sure the text of the expression is properly configured and will result in a single XML object value

Level: 1

Type: ERROR

Impact: Data

OSB-395106: Unexpected Error: the TokenSource does not contain an BEGIN ATTRIBUTE

Cause: There was an unexpected error while parsing the result of XQuery expression. A BEGIN ATTRIBUTE token was expected but not found

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-395107: Unexpected Error: the TokenSource does not contain an END ATTRIBUTE

Cause: There was an unexpected error while parsing the result of XQuery expression. A END ATTRIBUTE token was expected but not found

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-395108: Error parsing XML: {0}

Cause: There was an unexpected error while parsing the result of XQuery expression. There should be a message that points to the cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-395109: There was an error trying to migrate the contents of the xquery {0} to 1.0 engine: {1}

Cause: There was an unexpected error while migrating the contents of an xquery to 10 engine standard. There should be a message that points to the cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-395130: Exception in {0}, {1}

Cause: An unexpected exception occurred. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-395132: Selected WSDL binding is missing an operation ''{0}'' defined by corresponding port type

Cause: There was a problem while registering a WSDL-based service: The set of operations defined in the WSDL binding does not match exactly that of the corresponding port type

Action: Make sure the selected WSDL binding set of operations is exactly the same as that of the corresponding port type

Level: 1

Type: ERROR

Impact: Configuration

OSB-395133: Mismatch between the WSDL binding and the service definition type: {0}

Cause: There was an unexpected problem while registering a WSDL-based service: (1) the type of WSDL binding in WSDL resource is SOAP whereas the service is not of SOAP type or (2) there was a mismatch between the SOAP versions of the service and the corresponding WSDL binding or (3) the binding from the WSDL is not supported

Action: Edit and save the service. If this does not help, contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-395134: You can only use a HTTP binding with verb="POST"

Cause: There was an problem while registering a WSDL-based service: corresponding WSDL binding was HTTP with non-POST verb, which is not allowed

Action: Correct the WSDL resource or choose another WSDL binding for the service

Level: 1

Type: ERROR

Impact: Configuration

OSB-395135: Selected WSDL binding contains mixed-style operations and is not supported

Cause: There was a problem while registering a WSDL-based service: Some of the operations in the WSDL binding are of style ''document'' while others are of ''rpc''. OSB only supports all rpc or all document, but not mixed.

Action: Make sure the selected WSDL binding does not contain mixed-style operations

Level: 1

Type: ERROR

Impact: Configuration

OSB-395136: The wsdl binding has more than one operation you must specify how to select the operations

Cause: There was an problem while registering a WSDL-based service: The WSDL binding has more than one operation, so you must specify how to select the operation in service registration wizard

Action: Check the service configuration and make sure that the operation selection algorithm is properly configured

Level: 1

Type: ERROR

Impact: Configuration

OSB-395137: No corresponding mapping was found in the service definition for the WSDL operation: {0}

Cause: No corresponding mapping was found in the service definition for the WSDL operation: {0}

Action: Check the service configuration and make sure that the operation selection algorithm is properly configured

Level: 1

Type: ERROR

Impact: Configuration

OSB-395138: The operation referenced in the service definition cannot be found in the WSDL: {0}

Cause: There was an problem while registering a WSDL-based service: The operation referenced in the service definition cannot be found in the WSDL: {0}

Action: Check the service configuration and make sure that the operation selection algorithm is properly configured

Level: 1

Type: ERROR

Impact: Configuration

OSB-395139: Two or more operations expect the same incoming message, you must use a selector different than message body

Cause: There was a problem registering a WSDL-based service: the specified operation selection algorithm was SOAP Body while the associated WSDL binding was such that it is impossible to distinguish different operations based on data in the body of the incoming SOAP message.

Action: Choose a different operation selection algorithm for the service or use a different WSDL binding

Level: 1

Type: ERROR

Impact: Configuration

OSB-395140: At least one operation could not be mapped for this selector algorithm, you should use a selector different than message body. Attempt to evaluate the operation, for example during WS-Security, Operational Branch processing etc. - may result in unexpected results.

Cause: There was a problem registering a WSDL-based service: the specified operation selection algorithm was SOAP Body or XML Payload while the associated WSDL binding was such that it is impossible to distinguish different operations based on data in the body/payload of the incoming message.

Action: Choose a different operation selection algorithm for the service. Another option is to update the WSDL in a way that it is compatible with the selection algorithm. For example, make sure that the WSDL messages have a single part defined by element.

Level: 1

Type: ERROR

Impact: Configuration

OSB-395141: Either there are duplicate values for the soapAction attribute for different operations in the selected WSDL binding or soapAction is not defined for at least one operation in the WSDL. Therefore SOAPAction header operation selection algorithm cannot be used

Cause: There was a problem registering a WSDL-based service: Either there are duplicate values for the soapAction attribute for different operations in the selected WSDL binding or soapAction is not defined for at least one operation in the WSDL. Therefore SOAPAction header operation selection algorithm cannot be used

Action: Choose a different operation selection algorithm for the service or use a different WSDL binding

Level: 1

Type: ERROR

Impact: Configuration

OSB-395142: You cannot select operations for business services

Cause: There registered business service is not properly configured: it is not allowed to have operation selection algorithm for business services

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-395143: At least one message type must be specified for the request or response. Both message types cannot be ''None''

Cause: There was a problem registering messaging type service: At least one message type must be specified for the request or response. Both message types cannot be ''None''

Action: Choose a message type other than ''None'' for either request or response message type

Level: 1

Type: ERROR

Impact: Configuration

OSB-395144: The schema defined for mixed type, cannot be found in the repository

Cause: There was a problem registering Messaging Type service: the corresponding XML schema resource was not found

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-395145: The schema defined for mixed type, cannot be parsed

Cause: There was a problem registering Messaging Type service: the corresponding XML schema resource could not be parsed

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-395146: The element defined for mixed type, cannot be found in the schema

Cause: There was a problem registering Messaging Type service: the specified element was not found in the XML schema resource

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-395147: The type defined for mixed type, cannot be found in the schema

Cause: There was a problem registering Messaging Type service: the specified type was not found in the XML schema resource

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-395148: The XPath expression for operation selection is not valid: {0}

Cause: The XPath expression for operation selection is not valid

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-395149: Two or more operations expect the same incoming message, you must use a selector different than payload type

Cause: There was a problem registering a WSDL-based service: the specified operation selection algorithm was Payload Type while the associated WSDL binding was such that it is impossible to distinguish different operations based on data in the body of the incoming SOAP message.

Action: Choose a different operation selection algorithm for the service or use a different WSDL binding

Level: 1

Type: ERROR

Impact: Configuration

OSB-395150: The Transport Header name is required for the current selection algorithm

Cause: The Transport Header name is required for the current selection algorithm.

Action: Provide a Transport Header name.

Level: 1

Type: ERROR

Impact: Configuration

OSB-395330: Invalid number of arguments

Cause: The number of arguments to custom XQuery function did not match that which was expected

Action: Please check the pipeline action configuration that uses the custom XQuery function to make sure it is configured properly

Level: 1

Type: ERROR

Impact: Configuration

OSB-395331: An unexpected error occurred, the runtime executor is in an illegal state.

Cause: An unexpected error has occured during the execution of XQuery or XSLT resource

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-395332: The XQuery expression used to specify the name of the XQuery resource did not result in a string value

Cause: The result of the XQuery expression is expected to be a single string value which is the full path to XQuery resource to execute

Action: Please check the XQuery expression to make sure it produces expected results. You can use Log action to see the value of this expression at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-395333: XQuery expression evaluates to an invalid XQuery resource name: ''{0}''.

Cause: XQuery expression did not return the valid XQuery resource name. It should evaluate to an existing XQuery resource at runtime.

Action: Make sure that XQuery expression should evaluate to a existing XQuery resource in OSB at runtime. You can use Log action to see the value of this expression at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-395334: The number of parameters for registered XQuery resource {0} does not match that given to it at runtime

Cause: The number of input parameters given to XQuery resource at runtime does not match the number that he resource requires

Action: Double-check that the number of input arguments supplied in dynamic XQuery configuration matches that of the XQuery resource to be used at runtime

Level: 1

Type: ERROR

Impact: Configuration

OSB-395335: XQuery resource {0} expected an XQuery expression for XQuery parameter {1} but none was found

Cause: Each parameter to an XQuery resource needs to have an XQuery expression configured to be bound as its value at runtime. One or more of the parameters to the given XQuery is missing an expression for its value

Action: Double-check that all of the parameters to the XQuery resource have been properly supplied in dynamic XQuery configuration

Level: 1

Type: ERROR

Impact: Configuration

OSB-395336: The value of input argument {0} cannot be null or an empty string

Cause: The input argument value to the XQuery function is {1}; the argument value should not be null or empty string

Action: Please check the input argument {0} value to make sure it does not result in a null or empty string..

Level: 1

Type: ERROR

Impact: Data

OSB-395337: CustomXPathFunctionManager: Error during initialization! File: {0}. Error: {1}

Cause: There was an error parsing the contents of file {0} containing custom XPath function definitions

Action: Please check the contents of the file and make sure it conforms to specified XML schema and all restrictions on supported Java methods/types, etc. are followed

Level: 1

Type: ERROR

Impact: Process

OSB-395339: No custom function with QName ''{0}'' exists

Cause: An unexpected error has occured during the execution of XQuery resource

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-395340: Custom function name needs to be a non-empty string

Cause: The name of the custom XPath function needs to be a non-empty string

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule

Level: 1

Type: ERROR

Impact: Configuration

OSB-395341: Custom function namespace needs to be a non-empty string

Cause: The namespace of the custom XPath function needs to be a non-empty string

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule

Level: 1

Type: ERROR

Impact: Configuration

OSB-395342: Custom function class name needs to be a non-empty string

Cause: The name of the Java class for the custom XPath function needs to be a non-empty string

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule

Level: 1

Type: ERROR

Impact: Configuration

OSB-395343: Custom function class method signature needs to be a non-empty string

Cause: The name of the Java class method for the custom XPath function needs to be a non-empty string

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule

Level: 1

Type: ERROR

Impact: Configuration

OSB-395344: Custom function class {0} needs to be public

Cause: The Java class for the custom XPath function needs to have public scope

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule

Level: 1

Type: ERROR

Impact: Configuration

OSB-395345: Custom Function class {0} has no methods

Cause: The Java class for the custom XPath function has no methods

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule

Level: 1

Type: ERROR

Impact: Configuration

OSB-395346: No method with signature ''{0}'' was found in class {1}

Cause: The Java class for the custom XPath function has no method with the specified signature

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule

Level: 1

Type: ERROR

Impact: Configuration

OSB-395347: Method ''{0}'' needs to be public static

Cause: The Java method for the custom XPath function has to be declared as public static

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule

Level: 1

Type: ERROR

Impact: Configuration

OSB-395348: Unsupported Java class {0} used by custom XPath function

Cause: One or more of the input arguments and/or return values from a custom XPath function has a Java type not currently supported by this feature

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule

Level: 1

Type: ERROR

Impact: Configuration

OSB-395349: Expected {0} arguments. Got: {1}

Cause: The number of input arguments passed into custom XQuery function at runtime does not match the number of expected arguments specified by its corresponding Java method signature

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule

Level: 1

Type: ERROR

Impact: Configuration

OSB-395350: Error invoking custom xquery java function: {0}

Cause: An runtime error has occured during the invocation of a custom XQuery function

Action: Check the server log and the corresponding exception stack trace to see additional information that might point to the cause of the error

Level: 1

Type: ERROR

Impact: Data

OSB-395351: CustomXPathFunctionManager: Error during initialization! File: {0} Error: {1}

Cause: There was an error during initialization reading the contents of one or more Jar files in ALSB_HOME config xpath-functions directory

Action: Please check the contents of the directory

Level: 1

Type: ERROR

Impact: Process

OSB-395353: CustomXPathFunctionManager: Custom function name ''{0}'' is not valid

Cause: Custom function name needs to be a valid NCName. See http://www.w3.org/TR/REC-xml-names/#NT-NCName for more information

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule

Level: 1

Type: ERROR

Impact: Configuration

OSB-395355: CustomXPathFunctionManager: Error during initialization! File: {0} Error(s): {1}

Cause: There was an error during initialization reading the contents of specified XML configuration file

Action: Check the custom XPath function configuration file(s) in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified XML schema

Level: 1

Type: ERROR

Impact: Configuration

OSB-395357: XPath can only be executed against XML or MFL content

Cause: The configured XPath expression refers to a message contents variable or other expression whose content is not XML. XPath can only be executed against XML or MFL content

Action: Please check the value the configured expression to make sure that it refers to valid XML content. One can use Log action to log the result of any expression including message context variables.

Level: 1

Type: ERROR

Impact: Data

OSB-395358: XQuery expression for input parameter resulted in null

Cause: The configured XQuery expression the result of which is used for input parameter to XSLT transformation resulted in null.

Action: Please check the configured expression to make sure it results in non-null value. One can use Log action to log the result of any XQuery expression.

Level: 1

Type: ERROR

Impact: Data

OSB-395359: No value could be bound to variable: {0}

Cause: The configured XQuery expression the result of which is used for named input variable to XSLT transformation resulted in null.

Action: Please check the configured expression to make sure it results in non-null value. One can use Log action to log the result of any XQuery expression.

Level: 1

Type: ERROR

Impact: Data

OSB-395360: Failed to parse configuration into typed XmlObject: {0}

Cause: There was an error while initializing OSB pipeline runtime state for a given service. The error occurred while parsing the saved configuration for service message flow

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-395361: The XQuery expression used to specify the name of the XSLT resource did not result in a string value

Cause: The result of the XQuery expression is expected to be a single string value which is the full path to XSLT resource to execute

Action: Please check the XQuery expression to make sure it produces expected results. You can use Log action to see the value of this expression at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-395362: XQuery expression evaluates to an invalid XSLT resource name: ''{0}''.

Cause: XQuery expression did not return the valid XSLT resource name. It should evaluate to an existing XSLT resource at runtime.

Action: Make sure that XQuery expression should evaluate to a existing XSLT resource in OSB at runtime. You can use Log action to see the value of this expression at runtime.

Level: 1

Type: ERROR

Impact: Data

OSB-395363: The number of parameters for registered XSLT resource {0} does not match that given to it at runtime

Cause: The number of input parameters given to XSLT resource at runtime does not match the number that he resource requires

Action: Double-check that the number of input arguments supplied in dynamic XSLT configuration matches that of the XSLT resource to be used at runtime

Level: 1

Type: ERROR

Impact: Configuration

OSB-395364: XSLT resource {0} expected an XQuery expression for XSLT parameter {1} but none was found

Cause: Each parameter to an XSLT resource needs to have an XQuery expression configured to be bound as its value at runtime. One or more of the parameters to the given XSLT is missing an expression for its value

Action: Double-check that all of the parameters to the XSLT resource have been properly supplied in dynamic XSLT configuration

Level: 1

Type: ERROR

Impact: Configuration

OSB-395365: CustomXPathFunctionManager: Error during XQuery 1.0 engine-specific initialization!

Cause: There was an error during initialization

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-395366: XPath expression invalid, not a selection: {0}

Cause: Only selection-type XPath expressions are supported

Action: Use a selection-type XPath expression

Level: 1

Type: ERROR

Impact: Data

OSB-397000: Exception in {0}, {1}

Cause: A general runtime error has occured in OSB resource management component There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-397007: The environment value "{1}" used in the configuration plan for "{0}" does not support the {2} action.

Cause: An attempt was made to perform an action against an environment value that doesn't support that action.

Action: Modify the configuration plan to correct the error.

Level: 1

Type: ERROR

Impact: Configuration

OSB-397008: An SLA alert rule name is required in the location for the {1} environment value action in the configuration plan for "{0}".

Cause: No SLA alert rule name was specified in the location for the environment value action.

Action: Modify the configuration plan to correct the error.

Level: 1

Type: ERROR

Impact: Configuration

OSB-397009: The SLA alert rule "{2}" specified in the location for the {1} environment value action was not found in "{0}".

Cause: The SLA alert rule name was not found.

Action: Modify the configuration plan to correct the error.

Level: 1

Type: ERROR

Impact: Configuration

OSB-397010: The customizations contain the following illegal environment variable types: {0}

Cause: The customizations should only use public env value types. Public env value types have a category of either environmental or operational.

Action: Update the customization to only use public env value types.

Level: 1

Type: ERROR

Impact: Configuration

OSB-397011: Location of the env value of type "{1}" used in the configuration plan for "{0}" is {4} which is out of bounds [{2},{3}] in resource.

Cause: Environment value's location is out of bounds from the accepted range.

Action: Check the passed env value's location. It should be in the valid range.

Level: 1

Type: ERROR

Impact: Configuration

OSB-397012: There are no valid locations in "{0}" for env value of type "{1}".

Cause: There are no valid locations for the env value.

Action: Check that env value is specified correctly.

Level: 1

Type: ERROR

Impact: Configuration

OSB-397013: The location "{2}" for env value of type "{1}" in the configuration plan for "{0}" must be a non-negative integer.

Cause: The location should be a non-negative integer.

Action: Ensure that the specified location is a non-negative integer.

Level: 1

Type: ERROR

Impact: Configuration

OSB-397014: No location specified for env value of type "{1}" in the configuration plan for "{0}".

Cause: No location specified.

Action: Specify a location.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398000: Exception in {0}, {1}

Cause: An unexpected error has occured in OSB runtime while processing a message. There should be a specific error message that points to the cause of the error

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-398014: Invalid Proxy URI: {0}

Cause: There was an error while processing the configuration for given proxy service: The URI specified was not valid. There should be an error message that points out a specific problem

Action: Check the URI for the proxy service to make sure it is valid

Level: 1

Type: ERROR

Impact: Configuration

OSB-398015: The service definition does not contain a reference to a wsdl

Cause: The WSDL-based service being registered is incorrectly configured: there was a problem retrieving its corresponding WSDL information

Action: Contact technical support

Level: 1

Type: ERROR

Impact: Configuration

OSB-398016: Error loading the WSDL from the repository: {0}

Cause: The WSDL-based service being registered is incorrectly configured: there was a problem retrieving its corresponding WSDL information. There should be an error message that points to the cause of the problem

Action: Contact technical support

Level: 1

Type: ERROR

Impact: Configuration

OSB-398017: The service definition contains a reference to a port not present in the wsdl: {0}

Cause: There was a problem while registering a WSDL-based service: specified WSDL port is not present in associated WSDL resource

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398018: The service definition contains a reference to a binding not present in the wsdl: {0}

Cause: There was a problem while registering a WSDL-based service: specified WSDL binding is not present in associated WSDL resource

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398023: You can only setup inbound web service security on proxy services

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398024: This WSDL does not support web service security, you must attach a policy first

Cause: A service defined by the WSDL requires web service security policy but the WSDL does not have any

Action: Attach ws-policy to the WSDL or configure custom ws-policy for the service

Level: 1

Type: ERROR

Impact: Configuration

OSB-398025: You can only setup a service account on business services

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398026: You can only use web service security with a SOAP binding

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398038: Proxy service "{0}" does not have a credential for web service security encryption (no service key provider has been specified). The ws-policy of operation "{1}" requires an encryption credential.

Cause: The ws-policy of the proxy service contains a confidentiality assertion, the proxy must have a reference to a service key provider

Action: In the security tab, assign a service key provider to the proxy service (the service key provider must have an encryption credential)

Level: 1

Type: ERROR

Impact: Configuration

OSB-398040: Proxy service "{0}" does not have a credential for web service security digital signatures (no service key provider has been specified). The ws-policy of operation "{1}" requires a digital signature credential.

Cause: The ws-policy of the proxy service contains an integrity assertion, the proxy must have a reference to a service key provider

Action: In the security tab, assign a service key provider to the proxy service (the service key provider must have a digital signature credential)

Level: 1

Type: ERROR

Impact: Configuration

OSB-398042: Proxy service "{0}" does not have a credential for outbound two-way SSL authentication (no service key provider has been specified)

Cause: At least one route out of the proxy service requires 2-way SSL, the proxy must have a reference to a service key provider

Action: In the security tab, assign a service key provider to the proxy service (the service key provider must have an SSL client authentication credential)

Level: 1

Type: ERROR

Impact: Configuration

OSB-398043: The ws-policy of operation "{2}" for proxy service "{0}" contains a confidentiality assertion but service key provider "{1}" does not have an encryption credential

Cause: The ws-policy of the proxy service requires encryption, the service key provider linked to the proxy service must have an encryption credential

Action: Edit the service key provider and assign it an encryption credential, or edit the proxy service and choose a different service key provider (in the security tab)

Level: 1

Type: ERROR

Impact: Configuration

OSB-398044: The ws-policy of operation "{2}" for proxy service "{0}" contains an integrity assertion but service key provider "{1}" does not have a digital signature credential

Cause: The ws-policy of the proxy service requires digital signatures, the service key provider linked to the proxy service must have a digital signature credential

Action: Edit the service key provider and assign it a digital signature credential, or edit the proxy service and choose a different service key provider (in the security tab)

Level: 1

Type: ERROR

Impact: Configuration

OSB-398046: Proxy service "{0}" has one or more routes to a service which requires 2-way SSL authentication, but the proxy service does not have a credential for outbound SSL (service key provider "{1}" does not have an SSL credential).

Cause: At least one route out of the proxy service requires 2-way SSL, the proxy must have a reference to a service key provider

Action: In the security tab, assign a service key provider to the proxy service (the service key provider must have an SSL client authentication credential)

Level: 1

Type: ERROR

Impact: Configuration

OSB-398052: Could not retrieve an X.509 certificate from PKI Credential provider [service key provider: "{0}", key alias: "{1}"]

Cause: An error occurred while calling the PKI Credential Mapper Provider lookup method

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398055: Business service "{0}" cannot be associated with a router

Cause: There was an unexpected error validating the configuration of business service {0}: business services cannot be associated with a message flow

Action: Checking service configuration and/or contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398056: WS-I Compliance failure ({0}): {1}

Cause: The body of request or response message does not conform to WS-I basic profile due to stated reason. This could happen when receiving request messages by OSB proxy services or response messages from business services enabled for WS-I compliance.

Action: Look at the specific error message and examine the payload to see why the body of the message fails WS-I compliance check

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-398059: Proxy service "{0}" has web service security configuration but either: 1) its WSDL does not have web service security policies, or 2) the <UsingPolicy> tag is missing from the WSDL. You must edit/save the proxy (that will remove the web service security configuration), or add web service security policies to the WSDL.

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398060: The ws-policy of operation "{1}" in proxy service "{0}" contains a concrete confidentiality assertion. Confidentiality assertions assigned to proxy services must be abstract, the encryption certificate must not be embedded in the policy.

Cause: The proxy service is a WS-Security (web services security) active intermediary. Its ws-policy includes a "confidentiality" assertion (this is a Oracle-proprietary policy assertion which specifies that the client must encrypt the request message). This confidentiality assertion is concrete. That means the policy includes a base-64 encoded certificate (in the /wssp:Confidentiality/wssp:KeyInfo/wssp:SecurityTokenReference/wssp:Embedded/wsse:BinarySecurityToken element). Proxy services should not have concrete confidentiality assertions on its policy because the proxy's encryption certificate is assigned through a service key provider.

Action: Make the policy abstract. To do this edit the policy and delete the SecurityToken and SecurityTokenReference child elements inside the /wssp:Confidentiality/wssp:KeyInfo element.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398061: The ws-policy of operation "{1}" in business service "{0}" contains an abstract confidentiality assertion. Confidentiality assertions assigned to business services must not be abstract, the encryption certificate must be embedded in the policy

Cause: The ws-policy of the business service includes a "confidentiality" assertion (this is a Oracle-proprietary policy assertion which specifies that request messages to this service must be encrypted). This confidentiality assertion is abstract. That means the policy does not include an embedded base-64 encoded server certificate. The confidentiality assertion must be concrete.

Action: Make the policy concrete. To do this edit the policy and make sure there are SecurityToken and SecurityTokenReference child elements inside the /wssp:Confidentiality/wssp:KeyInfo element. The value of the SecurityTokenReference element is an embedded base-64 encoded server certificate (it must be the server's encryption certificate). Consult Oracle Service Bus security documentation to find examples of what this policy should look like.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398062: An error occurred during web service security validation: {0}

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398063: There is an outbound call to operation "{1}" on service "{0}", this operation requires encrypted response messages; the proxy must be assigned to a service key provider

Cause: One or more nodes in the pipeline route messages to a service whose ws-policy specify that response messages to the proxy must be encrypted with the proxy's encryption key. The proxy service should have a reference to a service key provider from which OSB will get the proxy's encryption credential (OSB will send this certificate on the request message), but no service key provider reference has been assigned to the proxy.

Action: Edit the proxy service. In the security tab choose a service key provider (the service key provider must have an encryption credential).

Level: 1

Type: ERROR

Impact: Configuration

OSB-398064: There is an outbound call to operation "{1}" on service "{0}", this operation requires signed request messages; the proxy must be assigned to a service key provider

Cause: One or more nodes in the pipeline route messages to a service whose ws-policy require OSB to sign the request messages. The proxy service should have a reference to a service key provider from which OSB will get the proxy's digital signature credential, but no service key provider reference has been assigned to the proxy.

Action: Edit the proxy service. In the security tab choose a service key provider (the service key provider must have a digital signature credential).

Level: 1

Type: ERROR

Impact: Configuration

OSB-398065: There is an outbound call to operation "{1}" on service "{0}", this operation requires encrypted response messages but the service key provider does not have an encryption credential

Cause: One or more nodes in the pipeline route messages to a service whose ws-policy specify that response messages to the proxy must be encrypted with the proxy's encryption key. The service key provider assigned to this proxy does not have an encryption credential.

Action: Edit the service key provider and choose an encryption credential; or alternatively, edit the proxy service and -in the security tab- choose a different service key provider (one which has an encryption credential).

Level: 1

Type: ERROR

Impact: Configuration

OSB-398066: There is an outbound call to operation "{1}" on service "{0}", this operation requires signed request messages but the service key provider does not have a digital signature credential

Cause: One or more nodes in the pipeline route messages to a service whose ws-policy require OSB to sign the request messages. The service key provider assigned to this proxy does not have an encryption credential.

Action: Edit the service key provider and choose a digital signature credential; or alternatively, edit the proxy service and -in the security tab- choose a different service key provider (one which has a digital signature credential).

Level: 1

Type: ERROR

Impact: Configuration

OSB-398067: An error occurred during WSS policy attachment validation for the service {0} : {1}

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398068: Proxy service attribute cannot be set to true for a business service resource

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398069: Failed to start timer {0}: {1}

Cause: There was an unexpected error while collecting statistics in OSB service runtime during the processing of a message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-398070: Failed to increment counter {0}: {1}

Cause: There was an unexpected error while collecting statistics in OSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-398071: Failed to stop timer {0}: {1}

Cause: There was an unexpected error while collecting statistics in OSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Process

OSB-398072: Proxy must invoke either a Pipeline, a Split-Join, a Business Service or another Proxy

Cause: A Proxy Service Resource must be wired to one of four resources: a Pipeline, a Split-Join, a Business Service or another Proxy

Action: Check the proxy service configuration and wire it as needed

Level: 1

Type: ERROR

Impact: Configuration

OSB-398073: Proxy may not invoke {0}. It must invoke either a Pipeline, a Split-Join, a Business Service or another Proxy

Cause: A Proxy Service Resource must be wired to one of four resources: a Pipeline, a Split-Join, a Business Service or another Proxy

Action: Check the proxy service configuration and wire it as needed

Level: 1

Type: ERROR

Impact: Configuration

OSB-398074: A Proxy service may not invoke itself directly or indirectly

Cause: A Proxy Service Resource must be wired to one of four resources: a Pipeline, a Split-Join, a Business Service or another Proxy

Action: Check the proxy service configuration and wire it as needed

Level: 1

Type: ERROR

Impact: Configuration

OSB-398075: A Proxy service of type {0} may not invoke service {1} of type {2}

Cause: A Proxy Service Resource can only invoke a service of compatible type. Also, when a proxy services that invokes another proxy or business service directly, service binding types have to match exactly

Action: Check the proxy service configuration and wire it as needed

Level: 1

Type: ERROR

Impact: Configuration

OSB-398076: The operation selection of a WSDL-typed pipeline {0} invoked by a WSDL-typed proxy service must either be none or match that of the invoking proxy service

Cause: The operation selection of a WSDL-typed pipeline invoked by a WSDL-typed proxy service must either be none or match that of the invoking proxy service

Action: Check the proxy service configuration and wire it as needed

Level: 1

Type: ERROR

Impact: Configuration

OSB-398077: Operation selection must be specified by the invoked pipeline {0}

Cause: When an Any SOAP proxy invokes WSDL SOAP pipeline or Any XML proxy invokes WSDL XML pipeline, the pipeline resource must specify operation selection

Action: Check the proxy service configuration and wire it as needed

Level: 1

Type: ERROR

Impact: Configuration

OSB-398078: Component {0} may not be invoked because it exists in a different project

Cause: Invoked components (pipeline and split join resources) must be in the same project as the proxy service invoking them

Action: Check the proxy service configuration and wire it as needed

Level: 1

Type: ERROR

Impact: Configuration

OSB-398106: The ws-policy of operation "{1}" in service "{0}" contains an identity assertion. The business service should have a web service security service account, but none has been configured.

Cause: The ws-policy of operation "{1}" in service "{0}" contains an identity assertion. Only web service security username tokens are supported for identity purposes. This business service must have a web service security service account.

Action: Edit the business service. In the security tab, choose a web service security service account.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398107: The ws-policy for service "{0}" and operation "{1}" contains a policy assertion with qname "{2}". This assertion is not recognized. Make sure the namespace declaration and local-name are correct.

Cause: The ws-policy contains a policy assertion which is not recognized.

Action: Edit the ws-policy and make sure all policy assertions are supported by Oracle Service Bus.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398108: Business service "{0}" has web service security configuration but either: 1) its WSDL does not have web service security policies, or 2) the <UsingPolicy> tag is missing from the WSDL. You must edit/save the service (that will remove the web service security configuration), or add web service security policies to the WSDL.

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398110: Business service "{0}" has configuration for message-level custom token authentication. Message-level custom token authentication only applies to proxy services.

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398111: Proxy service "{0}" has configuration for message-level custom authentication. Message-level custom authentication is not valid on services with binary or text binding.

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398112: Operation "{1}" in proxy service "{0}" is configured for WS-Security authentication, but the proxy service is also configured for message-level custom token authentication. WS-Security authentication and message-level custom authentication are mutually exclusive.

Cause: WS-Security authentication and message-level custom authentication are mutually exclusive.

Action: Make sure your proxy service is not configured for both types of authentication. You may have to edit the proxy service or the ws-policy to make sure that at most one of these two techniques is used.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398113: Invalid custom authentication token selector: {0}

Cause: The XPath expression in the custom-token selector is invalid

Action: Enter a valid XPath expression in the custom-token selector field

Level: 1

Type: ERROR

Impact: Configuration

OSB-398114: Invalid username selector: {0}

Cause: The XPath expression in the username selector is invalid

Action: Enter a valid XPath expression in the username selector field

Level: 1

Type: ERROR

Impact: Configuration

OSB-398115: Invalid password selector: {0}

Cause: The XPath expression in the password selector is invalid

Action: Enter a valid XPath expression in the password selector field

Level: 1

Type: ERROR

Impact: Configuration

OSB-398116: Invalid user-defined authentication context property selector: {0}

Cause: The XPath expression in the user-defined property selector is invalid

Action: Enter a valid XPath expression in the user-defined property selector field

Level: 1

Type: ERROR

Impact: Configuration

OSB-398117: Invalid variable name in selector: "{0}"

Cause: The variable name in a custom-token must be either "header" or "body"

Action: Edit the proxy service. In the security tab, choose a valid message part for your custom-token.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398118: The ws-policy of operation "{1}" in proxy service "{0}" contains an Identity assertion for UsernameToken without password. Such UsernameTokens can only be used when the token is signed, however, this ws-policy does not have an Integrity assertion. Either add an Integrity assertion policy or change your Identity policy so that the UsernameToken includes a password.

Cause: A web service security username token without a password can only be trusted if the token itself is signed by the message producer.

Action: Edit the ws-policy and make sure it either forbids username tokens without password, or otherwise have the policy require a digital signature which covers the username token.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398120: The WSDL for the typed transport endpoint could not be accessed.

Cause: There was a problem retrieving the WSDL from the typed transport service endpoint at the time of service registration

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398121: Error loading the WSDL for the typed transport endpoint: {0}

Cause: There was a problem retrieving the WSDL from the typed transport service endpoint at the time of service registration. There should be an error message that points to the specific cause of the error

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398123: Missing sla-alerting element in the service entry element.

Cause: There was an unexpected error while validating service configuration: a required element "sla-alerting" was missing from the configuration

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398125: Logging element should not exist in the service entry element.

Cause: There was an unexpected error while validating service configuration: business service configuration cannot have "logging" element

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398126: sla-alerting element should not exist in the service entry element.

Cause: There was an unexpected error while validating service configuration: business service configuration cannot have "sla-alerting" element

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398127: pipeline-alerting element should not exist in the service entry element.

Cause: There was an unexpected error while validating service configuration: business service configuration cannot have "pipeline-alerting" element

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398128: One of the Web service policy attached is not allowed on service {0} because the service binding does not support it

Cause: The service definition is invalid; it should not contain any ws-policy configuration.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398129: An error occurred while computing the web service policy for service {0}: {1}

Cause: An error occurred while computing the web service policy for service. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398130: Service "{0}" must have RM (reliable messaging) policy assertions in its web service policy

Cause: WS transport services must have RM (reliable messaging) policy.

Action: Configure the service's ws-policy. Make sure it has RM policy assertions.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398131: This service should not have WebLogic Server 9.X-style security policy assertions

Cause: WS transport services cannot have WebLogic Server 9.X-style security policy assertions

Action: Configure the service's ws-policy. Make sure it does not have any WebLogic Server 9.X-style security policy assertions.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398132: RM (reliable messaging) policy assertions are not allowed on this service.

Cause: RM (reliable messaging) policy assertions are only allowed on ws-transport services.

Action: Either remove the RM policy assertions from the service's ws-policy or switch the service to the ws transport.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398133: The service is based on WSDL with Web Services Security Policies that are not natively supported by Oracle Service Bus. Please select 'OWSM Policies - From OWSM Policy Store' option and attach equivalent OWSM security policy. For the Business Service, either you can add the necessary client policies manually by clicking 'Add' button or you can let Oracle Service Bus automatically pick and add compatible client policies by clicking 'Add Compatible' button.

Cause: WS-SP 1.x assertions are not allowed in this version of Oracle Service Bus (except in some cases in WS Transport endpoints)

Action: The service is based on WSDL with Web Services Security Policies that are not natively supported by Oracle Service Bus. Please select 'OWSM Policies - From OWSM Policy Store' option and attach equivalent OWSM security policy. For the Business Service, either you can add the necessary client policies manually by clicking 'Add' button or you can let Oracle Service Bus automatically pick and add compatible client policies by clicking 'Add Compatible' button.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398134: Proxy service {0} is marked as a web service security intermediary but does not have web service security policies

Cause: A web service security intermediary proxy service must have security policy (in it ws-policy).

Action: If you want this proxy service to be a web service security intermediary, edit the service's ws-policy and make sure it includes security policy. If on the other hand you do not want this proxy service to be a web service security intermediary, go to the security tab and click "update" (without making any other changes).

Level: 1

Type: ERROR

Impact: Configuration

OSB-398135: Business service {0} has a service account reference for web service security authentication but does not have web service security policies

Cause: A web service security service account is only meaningful if the business service has web service security policy (in its ws-policy). This business service has a reference to a web service security service account (although you may not be able to see it in the console).

Action: Either add security policy to this service's ws-policy or go to the security tab and click "update"(without making any other changes).

Level: 1

Type: ERROR

Impact: Configuration

OSB-398136: Proxy service {0} is enabled for content streaming and cannot be marked as a web service security intermediary

Cause: Content streaming feature is not allowed if your service is configured as a web service security active intermediary.

Action: Edit the service and turn off content streaming feature

Level: 1

Type: ERROR

Impact: Configuration

OSB-398137: Proxy service {0} is enabled for content streaming and perform custom authentication

Cause: Content streaming feature is not allowed if your service is configured for custom authentication.

Action: Edit the service and turn off content streaming feature

Level: 1

Type: ERROR

Impact: Configuration

OSB-398138: WSI-Compliance cannot be checked in proxies enabled for content streaming

Cause: WSI-Compliance cannot be checked in proxies enabled for content streaming.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398139: {0} is a soap/abstract soap type service, the service should have ws-policy configuration

Cause: soap/abstract soap type service should have ws-policy configuration

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398140: Proxy service "{0}" is a passive wss intermediary. The ws-policy of operation "{1}" contains an abstract confidentiality assertion but the proxy service does not have a service key provider reference or the referenced service key provider does not have an encryption credential. You will be able to invoke this proxy service but its effective WSDL will not have an encryption certificate. Clients must get this certificate out-of-band.

Cause: A passive WSS intermediary is a proxy service which has a WS-Security policy in its public WSDL (i.e., its "effective" WSDL), but which does not perform any WS-Security processing. It simply relays the security header to a back-end service. Whenever a passive WSS intermediary has an "abstract confidentiality" policy, the proxy should have a service key provider which, in turn, must have an encryption credential. This encryption credential will be then inlined in the effective WSDL.

Action: Edit the proxy service. In the security tab, choose a service key provider (the service key provider must have an encryption credential).

Level: 1

Type: ERROR

Impact: Configuration

OSB-398141: One or more ws-policies have been bound to operation "{0}" but there is no such operation

Cause: The service has custom ws-policy. One of the custom ws-policies is assigned to an operation which does not exist in the WSDL. This may be the result of a change in the WSDL.

Action: Either edit the WSDL and add the missing operation, or if no such operation exists, edit the service, go to the policy tab and click "update" (without making any other changes).

Level: 1

Type: ERROR

Impact: Configuration

OSB-398142: One or more ws-policies have been bound to the response of operation "{0}" but the operation is one-way

Cause: The service has custom ws-policy. One of the custom ws-policies is assigned to the response message of an operation which is declared in the WSDL to be a one-way operation. Such operations do not have response messages. This may be the result of a change in the WSDL.

Action: Edit the service, go to the policy tab and click "update" (without making any other changes).

Level: 1

Type: ERROR

Impact: Configuration

OSB-398143: A reliable messaging policy is bound to operation "{0}"; reliable messaging policies can only be bound to the service as a whole

Cause: RM (reliable messaging) policies cannot be bound to specific operations, they can only be bound to the entire service.

Action: Edit the service's ws-policy. Make sure RM policies are bound to the service as a whole.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398147: Service {0} is enabled for XOP/MTOM and cannot be marked as a web service security intermediary

Cause: XOP/MTOM feature is not allowed if your service is configured for as active message-level security intermediary

Action: Edit the service and turn off XOP/MTOM feature

Level: 1

Type: ERROR

Impact: Configuration

OSB-398148: Service {0} is enabled for XOP/MTOM and perform custom authentication

Cause: XOP/MTOM feature is not allowed if your service is configured for custom authentication.

Action: Edit the service and turn off XOP/MTOM feature

Level: 1

Type: ERROR

Impact: Configuration

OSB-398149: Only SOAP Document-style WSDL bindings are supported for REST services

Cause: Only SOAP Document-style WSDL bindings are supported for REST services

Action: Edit the service WSDL to select another binding

Level: 1

Type: ERROR

Impact: Configuration

OSB-398150: The service definition does not contain a reference to a WADL

Cause: The REST service being registered is incorrectly configured: there was a problem retrieving its corresponding WADL information

Action: Contact technical support

Level: 1

Type: ERROR

Impact: Configuration

OSB-398151: User-defined property name is empty or not valid.

Cause: user-defined property name is either not provided or invalid

Action: Enter a valid name in the user-defined property name field

Level: 1

Type: ERROR

Impact: Configuration

OSB-398204: [OSB Tracing] Internal Error while tracing message {0}

Cause: This is an informational message from OSB tracing subsystem that is logged whenever it fails to trace a particular message (inbound/outbound request/response)

Action: No action is required

Level: 1

Type: ERROR

Impact: Other

OSB-398307: Result Caching is not supported on Proxy Services.

Cause: Result Caching is only valid on business services.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-398308: Result Caching is not supported on business service because it has no request-response operations.

Cause: Result Caching is only allowed on business services that use at least one request-response operation.

Action: Edit the service configuration and either use a wsdl that defines a request/response operation or do not enable the result caching feature.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398310: Invalid Cache Token expression: {0}

Cause: The Cache Token XQuery expression is invalid

Action: Enter a valid XQuery expression in the Cache Token Expression field

Level: 1

Type: ERROR

Impact: Configuration

OSB-398312: Invalid Expiration Time expression: {0}

Cause: The Expiration Time XQuery expression is invalid

Action: Enter a valid XQuery expression in the Expiration Time Expression field

Level: 1

Type: ERROR

Impact: Configuration

OSB-398313: Cache expression is using invalid variable {0}.

Cause: The Cache XQuery expression is using an invalid variable. It should only be using $body, $header, $operation or $metadata.

Action: Ensure that the Cache XQuery expression only uses valid variables.

Level: 1

Type: ERROR

Impact: Configuration

OSB-398314: There was an error getting the result: {0}.

Cause: An exception was thrown when getting the result to be cached. The detail message should provide more information about the actual cause.

Action: Correct the error described in the exception message.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-398325: An error has occurred while parsing the payload. Payload details:{0}Exception:{1}

Cause: An exception occurred while parsing the inbound request or outbound response payload as XML. The exception message should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-398350: Error marking the following URIs offline as they are not part of {0}: {1}

Cause: An attempt was made to mark a URI offline that is not one of the URLs configured in the business service endpoint configuration.

Action: Check that the URI is part of the Business Service endpoint configuration before trying again.

Level: 1

Type: ERROR

Impact: Other

OSB-398351: WSI-Compliance option can only be enabled for SOAP 1.1 services

Cause: WSI-Compliance option can only be enabled for SOAP 1.1 services

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-473000: Failed to receive statistics from server {0} at tick {1}

Cause: The exception will detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473001: Error while aggregating statistics data for nexttick={0} and lastprocessedtick={1}.

Cause: The exception will detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473003: Aggregation Server Not Available. {0}

Cause: The exception will detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473004: Cannot recover from persistent Store.

Cause: The exception will detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473006: Failed to initialize statistics data structure after checkpoint {0}

Cause: The exception will detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473008: Aggregator rejected statistics reported by server {0} with tick {1}. The last processed tick by Aggregator is {2}.

Cause: This is caused when the statistics for a server are received by the Aggregator too late.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473010: Aggregator rejected statistics reported by server {0} with tick {1} because the server snapshot version {2} is not compatible with current snapshot versions {3}.

Cause: This happens when the snapshot sent to the Aggregator has a different snapshot version that the current snapshot version.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473013: Failed to send statistics to aggregation server: {0}

Cause: The exception will detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473014: Writing to Persistence Store Failed: {0}

Cause: The exception will detail the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473050: Monitoring has been disabled for the domain

Cause: Monitoring for this domain has been disabled. When the monitoring is disabled statistics are not collected. Hence you cannot retrieve statistics while monitoring is disabled.

Action: Enable monitoring for this domain. Go to Global Settings under System Administration and enable monitoring. You need to open a session using change center to do this.

Level: 1

Type: ERROR

Impact: Other

OSB-473051: Aggregator did not receive statistics from {0} for the current view

Cause: There is a communication failure between Aggregator server and other managed servers. One of the managed servers failed to send statistics to the managed server on which Aggregator is running.

Action: Wait for some time and try again.

Level: 1

Type: ERROR

Impact: Other

OSB-473052: Reset statistic Task Failed {0}

Cause: There is an error while trying to reset the statistics. There may be a problem while creating a session and committing it in the background.

Action: Wait for some time and try again.

Level: 1

Type: ERROR

Impact: Other

OSB-473053: Reset Unsuccessful: Weblogic Session lock held by user

Cause: A lock already exists on WLS Configuration. Some one opened a session on Weblogic for editing WLS configuration.

Action: Release the existing lock on weblogic server and try again. Go to weblogic console and Activate or Undo all changes.

Level: 1

Type: ERROR

Impact: Other

OSB-473055: Failed to get {0} from {1} due to {2}

Cause: Information about a service could not be retrieved. This may be because the service is not found in the domain. Service could have been deleted, renamed, moved or never existed.

Action: Check if the service exists and try with correct service ref again.

Level: 1

Type: ERROR

Impact: Other

OSB-473056: Failed to reset statistics for {0} services due to {1}

Cause: There is an error while trying to reset the statistics. There may be a problem while creating a session and committing it in the background.

Action: Wait for some time and try again.

Level: 1

Type: ERROR

Impact: Other

OSB-473057: Failed to get statistics for services due to {0}

Cause: There is a problem while trying to retrieve statistics for a service. This may be because the arguments passed to the API are not proper.

Action: Check the arguments passed to API and try again.

Level: 1

Type: ERROR

Impact: Other

OSB-473058: Failed to get statistics for services as operation {0} returned null.

Cause: Monitoring runtime did not return any statistics for a service.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473059: INTERNAL_PROCESSING_ERROR: {0}

Cause: Used to represent an internal error in the monitoring runtime. This may be because an unrecognized statistic type is returned by the monitoring runtime.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473060: INTERNAL_PROCESSING_ERROR: {0} due to {1}

Cause: Used to represent an internal error in the monitoring runtime.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473062: {1} is incorrect value for parameter {0} as it specifies a bitmap which does not represent valid combinations of resource types.

Cause: You should send a valid combination of bits while retrieving statistics. The values from 1 to 15 are allowed.

Action: Correct the resourceTypes argument and try again.

Level: 1

Type: ERROR

Impact: Other

OSB-473063: {1} is incorrect value for parameter {0} as it specifies a bitmap that has bits set for one or more resource types, which are not applicable to the service.

Cause: This is because you have requested statistics for a resource type which is not applicable for the service.

Action: Correct the bit combination and try again

Level: 1

Type: ERROR

Impact: Other

OSB-473064: Parameter {0} is invalid as it contains one or more {1} services.

Cause: You would have requested for business service statistics but you have sent a proxy ref as an argument to API. Or you would have requested for proxy service statistics but you have sent a business service ref as an argument to API.

Action: Correct the ref array argument and try again.

Level: 1

Type: ERROR

Impact: Other

OSB-473065: Could not find service - {0}. It is either renamed or moved or deleted or never existed...

Cause: The service for which you are trying to retrieve statistics does not exist. It may have been deleted, moved, renamed or never existed.

Action: Check if the service exists and try with the correct service ref.

Level: 1

Type: ERROR

Impact: Other

OSB-473066: Monitoring has been disabled for the service - {0}

Cause: Monitoring has been disabled for the service for which you are trying to retrieve or reset statistics.

Action: Enable the monitoring for this service. Go to View Proxy/Business Service page and click on Operational Settings Tab. You can enable monitoring here. To do this you need to open a session using change center.

Level: 1

Type: ERROR

Impact: Other

OSB-473067: The value of parameter {0} is invalid as {1}.

Cause: One of the argument passed to public API contains an invalid value.

Action: Correct the arguments to API and try again.

Level: 1

Type: ERROR

Impact: Other

OSB-473068: The value of aggregation interval {0} is invalid.

Cause: The service cannot be monitored at the specified Aggregation Interval.

Action: Change the Aggregation Interval to one of the valid aggregation Intervals.

Level: 1

Type: ERROR

Impact: Other

OSB-473069: Failed to read reset record for {0}

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473070: Failed to reset statistics

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473071: Failed to shutdown collector

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473072: Failed to shutdown aggregator

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473075: Could not compute information for {0}

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473076: Snapshot version incompatible

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473077: Exception in ClusterTimerPersistenceStore

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473078: Cannot contact Admin server. Therefore constructing the Cluster Authority Current time with the time skew 0

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473079: Cannot contact the admin server. Therefore constructing the Cluster Authority Urzeit from the persisted value

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473080: Error while closing the JNDI context

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-473500: JMS Reporting Data Manager failed to deploy during server start up {0}

Cause: The JMS Reporting Data Manager failed to deploy during server start up. This could be caused by insufficient Security privileges, missing Reporting Tables, or a lost Database Connection.

Action: Please verify the user's Security privileges and the existence of Reporting Tables and/or a Database Connection If there are no Reporting Tables, please run the JMS Reporting Provider Database Script.

Level: 1

Type: ERROR

Impact: Deployment

OSB-473501: The JMS Reporting Data Manager failed to undeploy {0}

Cause: There was a problem with un-deployment: all of the messages were already processed.

Action: Please contact Oracle Support with your log details.

Level: 1

Type: ERROR

Impact: Deployment

OSB-473502: Message reports are not persisted in the Reporting Table for MSG_GUID = {0} {1}

Cause: An unexpected error occurred when creating insert statement for message reports. There should be an error message that points to cause of the problem.

Action: Please contact Oracle Support with your log details.

Level: 1

Type: ERROR

Impact: Data

OSB-473503: A SQL Exception occurred during Message Reporting. Persistence with the SQL State is {0} and the Error Code is {1} {2}

Cause: A SQL Exception occurred while Message Reports were being inserted into the Message table.

Action: Please refer to the log for the source of the failure or contact Oracle Support.

Level: 1

Type: ERROR

Impact: Data

OSB-473504: The JMS Report Data Handler failed to send the message to the JMS Queue : {0} {1}

Cause: The JMS Report Data Handler failed to send a message to the JMS Queue. There may be no JMS Connection Factory or the data may be invalid.

Action: Please refer to the log for the source of the failure or contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-473505: JMS Reporting does not support this type of Database : {0}

Cause: JMS Reporting does not support this type of Database.

Action: Please use a supported Database type. These types include: ORACLE, SQL Server, DB2, SYBASE.

Level: 1

Type: ERROR

Impact: Installation

OSB-473506: An Error occurred while determining the Database type {0}

Cause: The type of Database may not be supported or the Database may be disconnected.

Action: Please check your Database connection and that you are using a supported Database type. These types include: ORACLE, SQL Server, DB2, SYBASE.

Level: 1

Type: ERROR

Impact: Network

OSB-473507: JMS Reporting does not support this type of Database.

Cause: JMS Reporting does not support this type of Database.

Action: Please use a supported Database type. These types include: ORACLE, SQL Server, DB2, SYBASE.

Level: 1

Type: ERROR

Impact: Installation

OSB-473508: The Database connection is disconnected {0}

Cause: Database connection has been lost.

Action: Please check the Database connection.

Level: 1

Type: ERROR

Impact: Network

OSB-473509: The ReportingMDB received an invalid Object {0} and the message will not be processed {1}

Cause: The ReportingMDB received an invalid Object for processing. It requires a ReportMessage type object.

Action: Please contact Oracle Support.

Level: 1

Type: ERROR

Impact: Data

OSB-473510: An unexpected error occurred while processing the message in ReportingMDB {0}

Cause: An unexpected error occurred while processing the message in ReportingMDB.

Action: Please refer to the log for the source of the error or contact Oracle Support

Level: 1

Type: ERROR

Impact: Data

OSB-473511: Failed to lookup the JNDI Provider for the JMS Reporting datasource {0}

Cause: Failed to look up the configured JNDI Provider for the JMS Reporting datasource

Action: Please verify that the JNDI Provider referred to by JMS Reporting is up and running.

Level: 1

Type: ERROR

Impact: Network

OSB-473512: An error occured while retrieving the report data from the Reporting table.

Cause: An error occured while retrieving the report data from the Reporting table.

Action: Please contact Oracle Support.

Level: 1

Type: ERROR

Impact: Network

OSB-473513: The document type is not allowed: the Message Body Data must be a String, XmlObject, or Binary.

Cause: The document type is not allowed: the Message Body Data must be a String, XmlObject, or Binary.

Action: Please verify the Payload or contact Oracle support.

Level: 1

Type: ERROR

Impact: Data

OSB-473514: An unexpected error occurred while receiving the message in ReportingMDB {0}

Cause: An unexpected error occurred while receiving the message in ReportingMDB. The message will not be processed.

Action: Please refer to the log for the source of the failure or contact Oracle Support.

Level: 1

Type: ERROR

Impact: Data

OSB-473516: An invalid message format was received in ReportMDB {0}. The message will not be processed. {1}

Cause: An Invalid message format was received. The message will not be processed.

Action: Please verify the Payload or the Report action configuration.

Level: 1

Type: ERROR

Impact: Data

OSB-473517: The JMS Reporting Provider Database tables weren't created and the JMS Reporting Data Manager didn't deploy.

Cause: The JMS Reporting Provider Database tables weren't created and the JMS Reporting Data Manager didn't deploy.

Action: Please run the JMS Reporting Provider Database Script and restart the server.

Level: 1

Type: ERROR

Impact: Deployment

OSB-473518: An error occurred while inserting data into the Reporting Table with a batch update {0}

Cause: The Batch update failed.

Action: Please make sure batch update supports your database JDBC driver.

Level: 1

Type: ERROR

Impact: Data

OSB-473519: An error occurred when initializing the PurgingMDB {0}

Cause: Report messages will not be deleted due to an error in resource initialization.

Action: Please verify that the PurgingMDB is deployed and your database connection.

Level: 1

Type: ERROR

Impact: Deployment

OSB-473520: An error occurred while initializing the ReportingMDB and Database details.

Cause: The ReportingMDB and Database details were not initialized.

Action: Please verify your Database connection.

Level: 1

Type: ERROR

Impact: Deployment

OSB-473521: No transaction is available to process the Report Message.

Cause: No transaction is available to process the Report Message.

Action: Please refer to the log to determine why the transaction is unavailable and/or retry sending the request. If the problem persists, please contact Oracle support

Level: 1

Type: ERROR

Impact: Other

OSB-473522: An error occurred while inserting data into the Reporting Table with Batch Update {0}

Cause: The Batch Update failed.

Action: Please make sure the Batch Update supports the database JDBC Driver.

Level: 1

Type: ERROR

Impact: Data

OSB-473523: The document type is not allowed: the Message Body Data must be a String, XmlObject, or Binary.

Cause: The document type is not allowed: the Message Body Data must be a String, XmlObject, or Binary.

Action: Please verify the Payload.

Level: 1

Type: ERROR

Impact: Data

OSB-473524: Could not initialize PurgingMDB and Database details.

Cause: Could not initialize PurgingMDB and Database details.

Action: Please verify the Database Connection.

Level: 1

Type: ERROR

Impact: Deployment

OSB-473525: Failed to lookup the JNDI Provider for the JMS Reporting datasource {0}

Cause: Failed to look up the configured JNDI Provider for the JMS Reporting datasource

Action: Make sure that the JNDI provider referred to by JMS Reporting is up and running.

Level: 1

Type: ERROR

Impact: Network

OSB-473526: There is no Database connection.

Cause: There is no Database connection.

Action: Please verify the Network connection.

Level: 1

Type: ERROR

Impact: Network

OSB-473527: There is No Report Index.

Cause: There is a Missing Key-Value pair in the Report Action.

Action: Please add a Key-Value pair to the Report Action.

Level: 1

Type: ERROR

Impact: Data

OSB-482200: The operation {0} is not supported by the provider {1} for user/group {2}.

Cause: Certain management operations WebLogic Server authentication providers are optional. Not all authentication providers support these optional operations. For example, an authentication provider may not support user account creation.

Action: Choose a different authentication provider. If you still need help contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-482201: The user {2} in provider {1} does not have sufficient privileges to execute the operation {0}.

Cause: An attempt was made to perform an operation by a user which does not have sufficient privileges

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-482202: An exception {1} was generated when executing operation {0} for user/group {3} in provider {2}.

Cause: An unexpected error occurred

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-482203: The user {0} already exists in provider {1}.

Cause: An attempt to create a user account failed because a user account with the same username already exists

Action: Make sure the user account does not already exist (possibly on a different authentication provider). You may have to choose a different username for the new user account.

Level: 1

Type: ERROR

Impact: Other

OSB-482204: Invalid user/group {0} supplied.

Cause: An invalid user name or group name was entered.

Action: Make sure you enter a valid user name or group name.

Level: 1

Type: ERROR

Impact: Other

OSB-482205: Invalid password supplied for user {0}: {1}

Cause: The password you entered is invalid

Action: Enter a valid password

Level: 1

Type: ERROR

Impact: Other

OSB-482206: The group {0} already exists in provider {1}.

Cause: An attempt to create a group failed because the group already exists

Action: Make sure the group does not already exist (possibly on a different authentication provider). You may have to choose a different group name.

Level: 1

Type: ERROR

Impact: Other

OSB-494001: Internal error generating navigation menu. No CommandId initialized for action "{0}".

Cause: Internal error generating navigation menu. No CommandId initialized for action.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-494002: Internal error occurred in OSBConsole : {0}

Cause: An unexpected general purpose exception has occurred in OSB Console There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-494003: A request to redirect to an invalid target has been detected. Request={0} address={1} user={2}

Cause: An invalid request has been detected. They may be an open redirect attack. The console has output a critical message to the server log.

Action: Take action based upon provided exception details.

Level: 24

Type: INCIDENT_ERROR

Impact: Other

OSB-494004: A Cross-site request forgery (CSRF) has been detected. Task={0} address={1} user={2}

Cause: CSRF : The console has output a critical message to the server log.

Action: Take action based upon provided exception details.

Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-495001: Internal error generating navigation menu. No CommandId initialized for action "{0}".

Cause: Internal error generating navigation menu. No CommandId initialized for action.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-495002: Internal error occured in OSBConsole : {0}

Cause: An unexpected general purpose exception has occurred in OSB Console There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-495003: Cannot Create or Edit or Activate or Exit session because there are unexpected errors occurred: {0}

Cause: Cannot Create or Edit or Activate or Exit session because there are unexpected errors occurred. The exception should provide more detail.

Action: Retry the activation.

Level: 1

Type: ERROR

Impact: Other

OSB-800007: Invalid message.

Cause: Invalid message.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-800009: Invalid URI.

Cause: Invalid URI.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-800010: URI does not start with t3://

Cause: URI does not start with t3://

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-800016: Unable to suspend because ref: {0} could not be found.

Cause: Unable to suspend because the ref could not be found.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-800017: No end-point is registered with ref: {0}

Cause: No end-point is registerd with the given ref.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-800019: Unable to accept the connections and stopped listening on the server Dsp.

Cause: Unable to accept the connections and stopped listening on the server Dsp. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Network

OSB-800020: Unable to resume because ref: {0} could not be found.

Cause: Unable to resume because the ref could not be found.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-800021: Unable to start because ref: {0} could not be found.

Cause: Unable to start because the ref could not be found.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-800022: Unable to delete because ref: {0} could not be found.

Cause: Unable to delete because the ref could not be found.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-800024: Unable to get dispatch policies.

Cause: Unable to get dispatch policies. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-800028: DSP transport registration failed.

Cause: DSP transport registration failed. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Deployment

OSB-800029: Illegal TransportSender type.

Cause: Illegal TransportSender type.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-800030: Writing of response to the client is failed.

Cause: Writing of response to the client failed. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-800031: Unable to start the service: {0}

Cause: Unable to start the service. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-800032: Unable to activate the service: {0}

Cause: Unable to activate the service. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-800033: Scheduling it to workmanager is failed.

Cause: Scheduling to the workmanager failed. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-800034: DspTransport receiver is failed.

Cause: DSP Transport receiver failed. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-800037: No JMX Connector available.

Cause: No JMX Connector available.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-800039: DspConfig.xml not found

Cause: DspConfig.xml not found.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Data

OSB-800040: DSP Transport : incoming message is empty

Cause: The incoming message is empty.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-800041: Soap Fault Received: {0}

Cause: Soap Fault received.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-800042: Error sending message

Cause: Error sending message. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-800043: Error binding socket

Cause: Error binding socket. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Ports

OSB-800044: Error closing socket

Cause: Error closing socket. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Ports

OSB-800045: Error closing socket input stream

Cause: Error closing socket input stream. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Ports

OSB-800046: Error executing query

Cause: Error executing query. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-800047: Error processing query result

Cause: Error processing query result. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-800048: Invalid uri: {0}

Cause: The uri is invalid. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-800049: Error getting provider configuration

Cause: Error getting provider configuration. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-800050: Error searching for URI conflicts

Cause: Error searching for URI conflicts. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-800051: Error checking binding type

Cause: Error checking binding type. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-800201: No dvm element found

Cause: DVM document must have a dvm element.

Action: Add 'dvm' element to the document.

Level: 1

Type: ERROR

Impact: Process

OSB-800202: Columns missing in DVM

Cause: Domain names are must in a DVM document

Action: Add domain names to the DVM document

Level: 1

Type: ERROR

Impact: Process

OSB-800203: Rows are missing in DVM document.

Cause: DVM document must have rows.

Action: Add rows to the DVM document.

Level: 1

Type: ERROR

Impact: Process

OSB-800204: Empty or Null DVM.

Cause: String empty or null.

Action: Provide a valid a dvm string.

Level: 1

Type: ERROR

Impact: Process

OSB-800205: Xml is invalid

Cause: Xml is invalid

Action: Provide a valid dvm xml.

Level: 1

Type: ERROR

Impact: Process

OSB-800206: Exception in Dvm Exception {1}

Cause: Exception occured in Dvm function call

Action: Please refer to exception log and rectify the issue.

Level: 1

Type: ERROR

Impact: Process

OSB-800207: Dvm resource parsing failed. Error is {0}

Cause: Dvm resource parsing failed. The exception message should provide more detail.

Action: Check the server log for details.

Level: 1

Type: ERROR

Impact: Process

OSB-800253: Xref resource parsing failed. Error is {0}

Cause: Xref resource parsing failed. The exception message should provide more detail.

Action: Check the server log for details.

Level: 1

Type: ERROR

Impact: Process

OSB-800254: Empty or Null Xref.

Cause: String empty or null.

Action: Provide a valid a xref string.

Level: 1

Type: ERROR

Impact: Process

OSB-800255: Xml is invalid

Cause: Xml is invalid

Action: Provide a valid xref xml.

Level: 1

Type: ERROR

Impact: Process

OSB-800256: Exception in Xref Exception {1}

Cause: Exception occured in Xref function call

Action: Please refer to exception log and rectify the issue.

Level: 1

Type: ERROR

Impact: Process

OSB-2030750: Failed to register MBean

Cause: Failed to register MBean

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Deployment

OSB-2030751: Failed to register MBeans

Cause: Failed to register MBeans

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Deployment

OSB-2030800: Failed to refresh OSB-EM Discovery MBeans

Cause: Failed to refresh OSB-EM Discovery MBeans

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Deployment

OSB-2030801: Failed to register FMW EM Plugin OSBConfigurationMBean

Cause: Failed to register FMW EM Plugin OSBConfigurationMBean

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Deployment

OSB-2030852: Failed to import: {0}

Cause: Failed to import. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-2030853: Invalid plugin file: {0}

Cause: Invalid plugin file. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-2030854: Could not create plugin classloader: {0}

Cause: Could not create plugin classloader. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-2030855: Could not register plugin classloader: {0}

Cause: Could not register plugin classloader. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-2030856: Could not register transport: {0}

Cause: Could not register transport. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-2030857: Could not register resource: {0}

Cause: Could not register resource. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Configuration

OSB-2030900: Failed to initialize deployment handler.

Cause: Failed to initialize deployment handler. The exception should provide more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Deployment

OSB-2031000: Split-Join deployment error during activation:{0}

Cause: An unexpected error occured while deploying a new/updated Split-Join or un-deploying an existing Split-Join.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Deployment

OSB-2031001: The Activation of Split-Join resources could not be committed because the deployment session has already been closed.

Cause: The Activation of Split-Join resources could not be committed because the deployment session has already been closed. This is an invalid state that could be the result of other session (WLS, OSB) related issues.

Action: The deployment session has not been committed and the server may be in an inconsistent state. If the OSB session has been activated, try to undo and retry the activation. If the problem persists, restarting the server should unlock the sessions. Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Deployment

OSB-2031002: Load notifications for Split-Join resources cannot be started because a deployment session is already active.

Cause: A deployment session is already active at server startup and a session for the server load notifications cannot be created.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Deployment

OSB-2031003: Split-Join deployment error during load notification: {0}{1}

Cause: An unexpected error occured while deploying a Split-Join during server startup.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Deployment

OSB-2031004: Load notifications for Split-Join resources could not be committed because the session has already been closed.

Cause: Something has already closed the session. This should not happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Deployment

OSB-2031100: Error converting the response message (Split-Join: ''{0}'' LINK: ''{1}'' Service: ''{2}''): {3}{4}

Cause: An error occured trying to un-marshall the response of a service invocation. A generic fault will be raise in the Split-Join.

Action: Turn on transport level debug log to get more information regarding the response message. If the service being invoked is a proxy service, turning on tracing for that service may also provide more information on the message.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031101: Error converting the response fault (Split-Join: ''{0}'' LINK: ''{1}'' Service: ''{2}''): {3}{4}

Cause: An error occured trying to un-marshall the fault response of a service invocation. A generic fault will be raise in the Split-Join.

Action: Turn on transport level debug log to get more information regarding the response message. If the service being invoked is a proxy service, turning on tracing for that service may also provide more information on the message.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031102: Error creating the SOAP Fault from the response fault while calling Split-Join ''{0}'': {3}{4}

Cause: An error occured trying to marshall the fault response into a SOAP Fault. The fault response was processed as if this error did not occur. If an error handler was configured in the calling Split-Join for this fault, and a SOAP Fault variable was defined, then its content will be empty.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031200: Schema validation for {0} failed: {1}

Cause: The schema has been modified other than by the Split-Join editor

Action: Please edit Split-Join using the Split-Join editor

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031201: Failed to parse schema: {0}

Cause: The schema has been modified other than by the Split-Join editor

Action: Please edit Split-Join using the Split-Join editor

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031202: Failed to create validation meta data: {0}

Cause: An unexpected error occurred trying to create meta data from wsdl definitions referenced by Split-Join.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031203: Failed to validate Split-Join: {0}

Cause: An unexpected error occurred during validation of Split-Join

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031300: Variable {0} is assigned a null value.

Cause: The transformation (most probably an assign or replace in that case) did not return any value.

Action: Turn on tracing to check the data. Check the data expression for the given transformation. An empty result may be due to missing XML elements/attributes in the data, improper use of namespaces...

Level: 1

Type: ERROR

Impact: Other

OSB-2031301: Variable {0} is assigned an array of values.

Cause: The transformation (most probably an assign or replace in that case) returned more than one value.

Action: Turn on tracing to check the data. Check the data expression for the given transformation. Such result may happen for example if the selected XML elements/attributes correspond to repeating nodes (XML Schema maxOccurs > 1).

Level: 1

Type: ERROR

Impact: Other

OSB-2031310: Variable {0} targeted for replace is not XML.

Cause: The variable targeted for replace operation does not hold XML data.

Action: Check that in the Split-Join resource the variable {0} is defined by an XML element or complex type.

Level: 1

Type: ERROR

Impact: Other

OSB-2031311: Content targeted for replace is not an element or an attribute

Cause: Content targeted for replace is not an element or an attribute

Action: Check the value of the variable that is targeted for replace operation.

Level: 1

Type: ERROR

Impact: Other

OSB-2031312: An attribute may only be replaced with an attribute

Cause: An attribute may only be replaced with an attribute

Action: Check the value of the variable that is targeted for replace operation.

Level: 1

Type: ERROR

Impact: Other

OSB-2031313: An element or its contents may only be replaced with elements and simple values

Cause: An element or its contents may only be replaced with elements and simple values

Action: Check the value of the variable that is targeted for replace operation.

Level: 1

Type: ERROR

Impact: Other

OSB-2031320: A Delete action cannot delete a variable.

Cause: This is caused by an invalid XPath expression that is trying to delete the variable.

Action: Check the XPath expression of the Delete action. The XPath expression should not result in the selection of the variable itself (e.g. ".[0]").

Level: 1

Type: ERROR

Impact: Other

OSB-2031330: Variable {0} targeted for insert is not XML.

Cause: The variable targeted for insert operation does not hold XML data.

Action: Check the value of the variable that is targeted for insert operation.

Level: 1

Type: ERROR

Impact: Other

OSB-2031331: Content cannot be inserted before/after the variable itself.

Cause: The Insert is configured to insert before/after the result of the selection, but the result of the selection is the variable itself.

Action: Check the XPath expression of the Insert action. The XPath expression should not result in the selection of the variable itself (e.g. ".[0]").

Level: 1

Type: ERROR

Impact: Other

OSB-2031332: Failed to insert after.

Cause: Inserting the result of this expression after specified XPath resulted in an error.

Action: Check the value of the variable that is targeted for insert operation.

Level: 1

Type: ERROR

Impact: Other

OSB-2031333: Cannot insert as a child of an attribute

Cause: It is illegal to insert as a child of an attribute

Action: Check the value of the variable that is targeted for insert operation.

Level: 1

Type: ERROR

Impact: Other

OSB-2031334: Unable to insert after first child

Cause: Unable to insert after first child as there was no child elements of specified XPath expression

Action: Check the value of the variable that is targeted for insert operation.

Level: 1

Type: ERROR

Impact: Other

OSB-2031335: Unable to insert after last child

Cause: Unable to insert after child element

Action: Check the value of the variable that is targeted for insert operation.

Level: 1

Type: ERROR

Impact: Other

OSB-2031336: Only attributes may be inserted next to another attribute

Cause: Only attributes may be inserted next to another attribute

Action: Check the value of the variable that is targeted for insert operation.

Level: 1

Type: ERROR

Impact: Other

OSB-2031337: Only elements and simple values may be inserted next to or inside of another element

Cause: Only elements and simple values may be inserted next to or inside of another element

Action: Check the value of the variable that is targeted for insert operation.

Level: 1

Type: ERROR

Impact: Other

OSB-2031350: Parameter at index {1} in method "{0}" is assigned an array of values.

Cause: The parameter expression returned more than one value for the parameter at index {1} in method "{0}".

Action: Check the data expression for the given parameter. Such result may happen for example if the selected XML elements/attributes correspond to repeating nodes (XML Schema maxOccurs > 1).

Level: 1

Type: ERROR

Impact: Other

OSB-2031351: Parameter at index {1} in method "{0}" is of type XmlObject but the expression resulted in a simple type.

Cause: The parameter expression returned a simple type value instead of an XML fragment.

Action: Check the data expression for the given parameter. An XML fragment is expected but a simple type is returned.

Level: 1

Type: ERROR

Impact: Other

OSB-2031352: A NumberFormatException was raised for parameter at index {1} in method "{0}": {2}

Cause: A NumberFormatException was raised for parameter at index {1} in method "{0}" during the conversion from the simple type result to the expected java type.

Action: Check the data expression for the given parameter and the schema type of the result. The value returned does not match the expected java type.

Level: 1

Type: ERROR

Impact: Other

OSB-2031353: Callout to java method "{0}" resulted in exception: {1}

Cause: The java method specified in the Java Callout operation was invoked and resulted in an exception. The exception details should be part of the error message.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-2031354: Security exception while calling to java method "{0}". Service account: "{1}". {2}

Cause: There was an error while setting up the security context for java callout method. This could happen if there is a problem retrieving the credentials of specified service account. There should be a specific error message that will pinpoint the source of the problem.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-2031400: No Flow Reference specified.

Cause: While trying to create, retrieve or update a Flow Configuration, no reference was specified.

Action: Ensure a Flow Reference is specified

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031401: No configuration details specified.

Cause: While trying to create or update a Flow Configuration, no configuration details were specified.

Action: Ensure Flow configuration is specified

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031402: No operational values specified.

Cause: While trying to update the operational settings for a Flow, no operational settings were specified.

Action: Ensure that operational settings are specified

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031403: No operational settings query specified.

Cause: While trying to return a list of flow refs with a given set of operational values, no operational values were specified.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031404: Expecting ref of type '{0}' but received ref of type '{1}'.

Cause: A flow ref is expected but received incorrect ref.

Action: Please check that the passed is ref is correct and is of type flow ref.

Level: 1

Type: ERROR

Impact: Other

OSB-2031405: An exception occurred trying to suspend the transaction: {0}.

Cause: An unexpected exception occurred while suspending the transaction after invoking an external service.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031410: Error during conversion of fault response to source for Split-Join "{0}". Root cause: {1}

Cause: Message converter could not transform the fault message. The fault message is potentially invalid. The exception should provide more details about the actual error. An attempt will be made to return a fault response with a server error of type http://www.bea.com/alsb/flow/faults:responseProcessingFault.

Action: Make sure the fault message format is correct and conforms to the style/use specified in the wsdl associated with flow. Please correct the fault message and try again.

Level: 1

Type: ERROR

Impact: Other

OSB-2031411: Error during conversion of response to source for Split-Join "{0}". Root cause: {1}

Cause: Message converter could not transform the response message. The response message is potentially invalid. The exception should provide more details about the actual error. An attempt will be made to return a fault response with a server error of type http://www.bea.com/alsb/flow/faults:responseProcessingFault.

Action: Make sure the response message format is correct and conforms to the style/use specified in the wsdl associated with Split-Join. Please correct the response message and try again.

Level: 1

Type: ERROR

Impact: Other

OSB-2031412: Unable to dispatch fault response for "{0}" due to error creating response metadata. Root cause: {1}

Cause: This is an unexpected error. This should not normally happen.

Action: Please make sure product installation is complete. Restart the server. Make sure there are no errors during server startup. Make sure Split-Join is deployed correctly. If error persists, contact support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031413: Error during conversion of default server fault response to source for Split-Join "{0}". Root cause: {1}

Cause: Message converter could not transform the fault message. The fault message is potentially invalid. The exception should provide more details about the actual error.

Action: Make sure the fault message format is correct and conforms to the style/use specified in the wsdl associated with Split-Join. Please correct the fault message and try again.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031414: Unable to dispatch response for "{0}" due to error creating response metadata. Root cause: {1}

Cause: This is an unexpected error. This should not normally happen.

Action: Please make sure product installation is complete. Restart the server. Make sure there are no errors during server startup. Make sure Split-Join is deployed correctly. If error persists, contact support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031415: Error during scheduling response for "{0}". Root cause: {1}

Cause: The exception should provide the root cause for the error

Action: Please correct the error before trying again.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031416: No statistics were returned for Split-Join {0} and server {1}.

Cause: The exception should provide the root cause for the error

Action: Please correct the error before trying again.

Level: 1

Type: ERROR

Impact: Other

OSB-2031417: No statistics were returned for Split-Join {0}.

Cause: The exception should provide the root cause for the error

Action: Please correct the error before trying again.

Level: 1

Type: ERROR

Impact: Other

OSB-2031418: An exception occurred trying to resume the transaction: {0}.

Cause: An unexpected exception occurred while resuming the transaction on the response thread.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031500: Unable to determine which inbound messaging activity to deliver message to. The message matches multiple inbound messaging activities with the same operation ''{1}'' but different correlation sets.

Cause: The inbound message has been rejected because it matches more than 1 enabled inbound messaging activity with the same partner link and operation but different correlation sets. It cannot be determined which inbound messaging activity the message should be delivered to. This is potentially due to a timing issue. See WS-BPEL 2.0, section 10.4 for more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031501: The completion condition for counter ''{0}'' can never be true.

Cause: The counter will never complete. See WS-BPEL 2.0, section 11.7 for more detail.

Action: Revise the counter so that it can complete.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031502: An inbound messaging activity is already enabled for operation ''{1}''.

Cause: A receive activity was processed that, if successfully enabled, would have resulted in more than 1 receive waiting for the same message. If more than 1 receive is enabled for the same partner link, operation and correlation set it would result in multiple targets for inbound messages. This is potentially due to a timing issue. See WS-BPEL 2.0, section 10.4 for more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031503: An inbound messaging activity is already enabled for operation ''{1}''.

Cause: It is illegal to have more than 1 inbound messaging activity enabled with the same partner link, operation and message exchange token. See WS-BPEL 2.0, section 10.4.1 for more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031504: The counter ''{0}'' defines ''{1}'' iterations but the completion condition requires ''{2}'', so it will never complete.

Cause: The counter has processed to the point where it will never complete (For example, the counter may require 8 more iterations but there will only be 6). See WS-BPEL 2.0, section 11.7 for more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031506: The expression evaluated to a type of ''{1}'' but a type of ''{0}'' was expected.

Cause: An expression evaluated to an incompatible type for assignment. See WS-BPEL 2.0, sections 8.4.2 and 8.4.3 for more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-2031507: The message for operation ''{1}'' has not been replied to.

Cause: The partner link for an outstanding message exchange has just gone out of scope so the exchange will never be replied to. See WS-BPEL 2.0, section 10.4.1 for more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031508: Unknown message exchange for operation ''{1}''.

Cause: An attempt was made to reply to a non-existent message exchange. See WS-BPEL 2.0, section 10.4.1 for more detail.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031509: Executing an expression caused an unhandled fault: {0}.

Cause: An unexpected error occurred while executing an expression. The exception message should provide details of the cause.

Action: Correct the error specified in the exception message.

Level: 1

Type: ERROR

Impact: Other

OSB-2031510: The partner role ''{0}'' is uninitialized.

Cause: An attempt was made to access a partner link before it was initialized. This should never happen (it should be caught by validation during deployment).

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-2031511: The source for doXslTransform has {0} items, when exactly 1 is required.

Cause: The source for the doXslTransform function contains an XML document with other than 1 root node.

Action: Ensure that the source contains only 1 root node.

Level: 1

Type: ERROR

Impact: Other

OSB-2031512: The source for doXslTransform is of unsupported type ''{0}''. Supported types are {1}.

Cause: The source for doXslTransform is an unsupported type. This should never happen.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-2031513: The XSL stylesheet ''{0}'' was not found.

Cause: The XSL stylesheet could not be found on the class loader hierarchy.

Action: Ensure that the stylesheet can be found on the class loader hierarchy.

Level: 1

Type: ERROR

Impact: Other

OSB-2031514: The message for process ''{0}'' and operation ''{2}'' is rejected because a previous message for the same is waiting to be processed (possible out of order).

Cause: A message was received by the process for a partner link, operation and correlation sets when one is already waiting to be processed. One possible reason for this is that the messages were received out of order.

Action: Resend the message.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031515: The <from> element ''{0}''is not substitutable for the <to> element ''{1}''.

Cause: The EII selected by the from-spec is not substitutable for the EII selected by the to-spec. If the from-spec and the to-spec select EIIs with different element names, then the from-spec element must belong to the substitutionGroup of the to-spec element (as determined by the schema definitions for the elements).

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-2031518: Variable ''{0}'' is being referenced before it has been initialized with a value.

Cause: The variable is being referenced before it has been initialized. This is generally a problem with the process definition but it could be a timing issue.

Action: Modify the process to ensure that the variable is always initialized before it is referenced.

Level: 1

Type: ERROR

Impact: Other

OSB-2031519: Inbound message ''{0}'' cannot initialize variable because it is incomplete.

Cause: The inbound message is missing at least one part.

Action: Ensure that the message contains all the parts defined on the message type for the input message of the operation.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031520: Outbound message ''{0}'' cannot be sent because it is incomplete.

Cause: The outbound message is missing at least one part.

Action: Ensure that the message contains all the parts defined on the message type for the output message of the operation.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031521: Expression ''{0}'' returned {1} items when exactly 1 is required.

Cause: Expressions (particularly those used in Copy) should return a single item. If the expression evaluates to 0 or more than 1 item it is an exception.

Action: Ensure that the expression selects a single item.

Level: 1

Type: ERROR

Impact: Other

OSB-2031522: Nested transactions are not supported.

Cause: An attempt was made to start a new transaction when one was already active. This is not supported. This should never happen (because transactions cannot be explicitly started currently).

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

OSB-2031600: Correlation set ''{0}'' has an invalid initiate value of ''{1}''.

Cause: The correlation set has an invalid value. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031601: Unable to deliver the message for process ''{0}'' and operation ''{2}''. It does not match any start activity.

Cause: The inbound message does not match a start activity and it contains no correlation properties. As such, it will never be able to be delivered to a process instance.

Action: Either modify the message so it will correlate (different process, partner link, operation or correlation properties) or modify the process.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031602: Unable to deliver the message for process ''{0}'' and operation ''{2}''. It does not match any inbound messaging activities.

Cause: There are no inbound message activities for the partner link and operation of the message. The message cannot be delivered to any instance of the given process.

Action: Either modify the message so it does match an inbound messaging activity (different process, partner link or operation) or modify the process to match the message.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031603: The message for process ''{0}'' and operation ''{2}'' correlated to some inbound messaging activities but they were removed when the best matches were selected.

Cause: While correlating the incoming message, some messaging activities were found but after ranking them, there was no "best" match selected. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031604: The message for process ''{0}'' and operation ''{2}'' correlated to some inbound messaging activities on process instance ''{3}'' but the activities were removed when the best matches were selected.

Cause: While correlating the incoming message, a specific process instance was selected but there were no messaging activities for the partner link and operation. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031605: Unable to determine which process instance to deliver the message to. The message for process ''{0}'' and operation ''{2}'' matches multiple process instances.

Cause: The incoming message correlates to multiple process instances. This means that there was more than 1 process instance to which the message could be delivered.

Action: Either modify the message so it only matches one process instance (different process, partner link, operation or correlation properties) or modify the process.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031606: Unable to determine which start activity to deliver the message to. The message for process ''{0}'' and operation ''{2}'' matches multiple start activities.

Cause: The incoming message correlates to multiple start activities in the process instance. This means the message cannot be delivered. This is a problem with the process definition.

Action: Modify the process definition to define only a single start activity for the same partner link and operation.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031607: Unable to determine correlation properties. Correlation set ''{0}'' has not been initiated on process instance ''{1}''.

Cause: A correlation set that has an initiate value of "NO" has not been initiated. An initiate value of "NO" means that the correlation set should already be initiated before being used to correlate an inbound message.

Action: Modify the process to ensure that all correlation sets are initiated before they are used.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031608: Unable to determine correlation properties. Correlation set ''{0}'' has already been initiated.

Cause: A correlation set that has an initiate value of "YES" has already been initiated. An initiate value of "YES" means that the correlation set should NOT be initiated as it will be initiated using the values of the inbound message.

Action: Modify the process to ensure that correlation sets are NOT initiated before they should be.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031609: Unable to determine correlation properties. Correlation set ''{0}'' has different property values.

Cause: A message that has already been matched to a messaging activity has different correlation properties than the correlation set values associated to the messaging activity. This generally occurs for outbound messages (since the inbound messages wouldn't have matched this instance if they didn't match).

Action: Ensure that the outbound message has the same correlation properties as the messaging activity.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031610: Unable to deliver the message for process ''{0}'' and operation ''{2}''. It does not match any existing process instance.

Cause: While correlating the incoming message, message properties were calculated but did not match any existing process instance. It is possible that this message will match a process instance in the future.

Action: Resend the message.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031650: No value found for variable ''{0}'' and property ''{1}''.

Cause: The variable value does not contain the specified property.

Action: Ensure that the variable does contain the specified property.

Level: 1

Type: ERROR

Impact: Other

OSB-2031651: A selection operation returned a 'nil' XML.

Cause: The expression evaluated to an XML object specified as a 'nil' value.

Action: Ensure that the expression evaluates to a non-'nil' value.

Level: 1

Type: ERROR

Impact: Other

OSB-2031652: Scripting language ''{0}'' is not supported.

Cause: The scripting language is not supported. This should be caught by validation during deployment.

Action: Modify the process to use a supported scripting language.

Level: 1

Type: ERROR

Impact: Other

OSB-2031653: The context node is of unsupported type ''{0}'' when it is required to be of type ''{1}''.

Cause: The context node for the expression is not of the expected type. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031654: Variable ''{0}'' is a message. It must be either a variable defined by a schema type or a schema variable or a message part.

Cause: The variable used in the expression is defined as a message type. Message type variables cannot be referenced directly - only their parts can be referenced. This should be caught by validation during deployment.

Action: Modify the expression to use the $(variable).(part) syntax.

Level: 1

Type: ERROR

Impact: Other

OSB-2031655: Variable ''{0}'' is not a message but is being referenced as though it has a part ''{1}''.

Cause: The variable is being used via the $(variable).(part) but it is not a message type variable. This should be caught by validation during deployment.

Action: Modify the expression to use only $(variable) syntax.

Level: 1

Type: ERROR

Impact: Other

OSB-2031656: Variable ''{0}'', defined as message type ''{1}'', does not contain part ''{2}''.

Cause: The variable is defined by a message type that does not have the given part. This should be caught by validation during deployment.

Action: Modify the expression to use a part that the message type does have.

Level: 1

Type: ERROR

Impact: Other

OSB-2031657: The xml fragment for the literal has more than 1 root element.

Cause: An XML literal must have a single root element. This should be caught by validation during deployment.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031700: Trying to add a null input message to exchange for operation ''{1}''.

Cause: A null input message cannot be added to a message exchange. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031701: Trying to add a second input message to exchange for operation ''{1}''.

Cause: An input message can only be set once on a message exchange. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031702: Exchange for operation ''{1}'' does not support input messages.

Cause: An input message can only be added to a message exchange that is expecting an input message. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031703: Input message ''{0}'' is not for exchange with operation ''{2}''.

Cause: An input message can only be added to a message exchange if it is of the same message type as the input message in the WSDL operation for the message exchange. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031704: Trying to add a null output message to exchange for operation ''{1}''.

Cause: A null output message cannot be added to a message exchange. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031705: Trying to add a second output message to exchange for operation ''{1}''.

Cause: An output message can only be set once on a message exchange. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031706: Exchange for operation ''{1}'' does not support output messages.

Cause: An output message can only be added to a message exchange that is expecting an output message. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031707: Output message ''{0}'' is not for exchange with operation ''{2}''.

Cause: An output message can only be added to a message exchange if it is of the same message type as the output message in the WSDL operation for the message exchange. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031708: Trying to add a null fault message to exchange for operation ''{1}''.

Cause: A null fault message cannot be added to a message exchange. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031709: Trying to add a second fault message to exchange for operation ''{1}''.

Cause: A fault message can only be set once on a message exchange. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031710: Part ''{0}'' is not part of message ''{1}''.

Cause: The part is not defined in the message type. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031711: Message ''{0}'' is unknown.

Cause: The message type is unknown. This should never happen.

Action: Contact Oracle Support Servicesl Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031750: The <to> evaluates to null.

Cause: The ''to'' node of a copy evaluates to null. It should evaluate to a a non-null value.

Action: Ensure that the ''to'' node evaluates to a non-null value.

Level: 1

Type: ERROR

Impact: Other

OSB-2031751: The <from> evaluates to null.

Cause: The ''from'' node of a copy evaluates to null. It should evaluate to a a non-null value.

Action: Ensure that the ''from'' node evaluates to a non-null value.

Level: 1

Type: ERROR

Impact: Other

OSB-2031753: The value returned is a ''{0}'' when a boolean was required.

Cause: Conditions should evaluate to a boolean value but this condition did not.

Action: Ensure that the condition always evaluates to a boolean value.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031754: Received an unexpected response for invoke (operation is ''{0}'').

Cause: The Invoke received a response from the invocation but it was not expected because the exchange pattern was not IN_OUT.

Action: Ensure that the partner link being invoked has the expected exchange pattern.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031755: Expected a fault or output response for invoke but got neither.

Cause: The Invoke expected a response from the invocation but none was received.

Action: Ensure that the partner link being invoked has the expected exchange pattern of IN_OUT.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031757: The alarm definition ''{0}'' defines no deadline, duration or repeat interval.

Cause: An alarm must contain a deadline, duration or a repeat interval. This should be caught by validation during deployment.

Action: Modify the alarm to define a deadline, duration or a repeat interval.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031758: The value returned ''{0}'' must be positive.

Cause: A repeat interval must be a positive integer.

Action: Ensure that the repeat every interval expression evaluates to a positive integer.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031759: The expression ''{0}'' is an invalid deadline.

Cause: The deadline expression must evaluate to an XML Schema date or datetime.

Action: Ensure that the deadline expression evaluates to an XML Schema date or datetime.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031760: The expression ''{0}'' is an invalid duration. It should be in the form PnYnMnDTnHnMnS.

Cause: The duration expression must evaluate to an XML Schema duration. eg. For 1 day and 10 seconds use P1DT10S See http://www.w3.org/TR/xmlschema-2/#duration for details.

Action: Ensure that the duration expression evaluates to an XML Schema duration.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031762: WSDL operation for operation ''{1}'' not found.

Cause: The WSDL operation was not found in the process metadata. This should be caught by validation during deployment.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031763: The completion condition must be a number, but the expression evaluated to ''{0}''.

Cause: The completion condition must evaluate to an XML Schema unsigned integer.

Action: Ensure that the completion condition evaluates to an XML Schema unsigned integer.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031764: The completion condition value of ''{0}'' is invalid.

Cause: The completion condition must evaluate to a positive integer.

Action: Ensure that the completion condition evaluates to a positive integer.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031765: Timer expression ''{0}'' is invalid: {1}

Cause: The timer expression is not valid according to the XML Schema for deadlines or durations (depending on which expression it is). The exception message should indicate where the error is.

Action: Correct the expression according to the exception message.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031766: The date value ''{0}'' is invalid.

Cause: The date value is not a valid XML Schema date or datetime.

Action: Ensure that the date is a valid XML Schema date or datetime.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031768: The start counter value must be a number, but the expression evaluated to ''{0}''.

Cause: The start counter value must evaluate to an XML Schema unsigned integer.

Action: Ensure that the start counter value evaluates to an XML Schema unsigned integer.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031769: The start counter value of ''{0}'' is invalid.

Cause: The start counter value must evaluate to a positive integer.

Action: Ensure that the start counter value evaluates to a positive integer.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031770: A final counter value must be a number, but the counter evaluated to ''{0}''.

Cause: The final counter value must evaluate to an XML Schema unsigned integer.

Action: Ensure that the final counter value evaluates to an XML Schema unsigned integer.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031771: The final counter value ''{0}'' is invalid.

Cause: The final counter value must evaluate to a positive integer.

Action: Ensure that the final counter value evaluates to a positive integer.

Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031800: Resource ''{0}'' not found.

Cause: The specified resource cannot be found via the class loader.

Action: Ensure that the resource is on the class loader hierarchy.

Level: 1

Type: ERROR

Impact: Files

OSB-2031801: Resource ''{0}'' is invalid.

Cause: The resource does not conform to the http://www.bea.com/bpel/operation XML schema.

Action: Ensure that the resource conforms to the schema.

Level: 1

Type: ERROR

Impact: Other

OSB-2031802: XPath ''{0}'' is invalid for loading operations: {1}.

Cause: The XPath used in loading operations is a subset of XPath 1.0. The exception message should detail the reason it is invalid.

Action: Correct the errors detailed in the exception message.

Level: 1

Type: ERROR

Impact: Other

OSB-2031803: XPath defines no components.

Cause: The XPath used for loading operations contains no XPath steps.

Action: Ensure that the XPath contains at least one XPath step.

Level: 1

Type: ERROR

Impact: Other

OSB-2031804: Property ''{1}'' on class {0} is read only.

Cause: Unable to inject a value into the class for the property as there is no setter method.

Action: Either update preprocess.xml to not inject the property or add a public setter method.

Level: 1

Type: ERROR

Impact: Other

OSB-2031805: Property ''{1}'' on class {0} has an unsupported type.

Cause: Unable to inject a value into the class for the property as it is an unsupported type. Only simple JavaBean types are supported.

Action: Either remove the injection from preprocess.xml or change the property type.

Level: 1

Type: ERROR

Impact: Other

OSB-2031806: Property ''{1}'' on class {0} is not found.

Cause: Property does not exist on the class.

Action: Either remove the injection from preprocess.xml or add the property.

Level: 1

Type: ERROR

Impact: Other

OSB-2031807: An XmlObject that matches the xpath ''{0}'' has no line numbers.

Cause: The XmlObject was created without line numbers. Line numbers are required to use XPath expressions. This should not happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031808: The class {0} is not found.

Cause: The class {0} is not found.

Action: Ensure the class is on the classpath.

Level: 1

Type: ERROR

Impact: Other

OSB-2031809: An error occurred introspecting class {0}: {1}.

Cause: Unable to introspect on the class.

Action: Correct the errors detailed in the exception message.

Level: 1

Type: ERROR

Impact: Other

OSB-2031810: An error occurred create a new instance of class {0}: {1}.

Cause: Unable to create a new instance of the class.

Action: Correct the errors detailed in the exception message.

Level: 1

Type: ERROR

Impact: Other

OSB-2031856: Partner link {0} not found.

Cause: A partner link was not found.

Action: Ensure that the partner link is in scope.

Level: 1

Type: ERROR

Impact: Other

OSB-2031857: Correlation set {0} not found.

Cause: A correlation set was not found.

Action: Ensure that the correlation set is in scope.

Level: 1

Type: ERROR

Impact: Other

OSB-2031858: Thread {0} has a job in the job queue.

Cause: An attempt was made to create a new job for the thread but there is already a job in the job queue for it. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031859: The job queue capacity has been reached. No more jobs can be added.

Cause: The job queue capacity has been reached. No more jobs can be added. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031860: Thread {0} has an invalid status.

Cause: An attempt was made to start processing the given thread but it's status is invalid for processing. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031900: Variable type ''{0}'' is unsupported.

Cause: The variable type is unsupported. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031901: <to> must evaluate to a message.

Cause: The ''to'' value should be a message. This should be caught by validation during deployment.

Action: Ensure that the ''to'' value evaluates to a message.

Level: 1

Type: ERROR

Impact: Other

OSB-2031902: <from> must evaluate to a message.

Cause: The ''from'' value should be a message. This should be caught by validation during deployment.

Action: Ensure that the ''from'' value evaluates to a message.

Level: 1

Type: ERROR

Impact: Other

OSB-2031903: <to> is a ''{0}'' message but <from> is a ''{1}'' message.

Cause: The ''to'' and ''from'' need to be the same message type. This should be caught by validation during deployment.

Action: Ensure that the ''from'' and ''to'' evaluates to messages of the same message type.

Level: 1

Type: ERROR

Impact: Other

OSB-2031904: Creating partner links is not supported.

Cause: Creating partner links is not supported. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031905: Cloning partner links is not supported.

Cause: Cloning partner links is not supported. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031906: <to> must be a partner link.

Cause: An attempt was made to set a non-partner link value to a service reference. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031907: Creating text nodes is not supported.

Cause: Creating text nodes is not supported. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031908: Cloning text nodes is not supported.

Cause: Cloning text nodes is not supported. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031909: <to> must be a text node.

Cause: An attempt was made to set a non-text node value to a text value. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031910: <to> must be an xml object.

Cause: An attempt was made to set a non-XML object value to an XML object. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2031911: Variable ''{0}'' is invalid: {1}.

Cause: A variable has an invalid value. The reason should be specified in the exception message.

Action: Correct the error as detailed in the exception message.

Level: 1

Type: ERROR

Impact: Other

OSB-2031912: The keepSrcElementName attribute has been set but the from-spec and to-spec are not both EIIs.

Cause: The keepSrcElementName on the Copy element is only allowed to be used when both the from-spec and to-spec are EIIs. If either the from-spec or to-spec is NOT an EII, the keepSrcElementName MUST NOT be explicitly set.

Action: Ensure that the expressions for the from-spec and to-spec select EIIs.

Level: 1

Type: ERROR

Impact: Other

OSB-2032000: Error during invocation of "{0}" for event "{1}" of type "{2}".

Cause: There are several reasons for the invocation to fail. The exception must provide details to help identify the reason for the failure.

Action: Fix the artifact based on the exception. If the exception is not clear contact support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032001: Fatal error: Unable to invoke "{0}" for event "{1}" of type "{2}" as "{0}" does not exist.

Cause: The artifact invoked does not exist. This is probably due to the fact that there were errors during deployment or the session used to deploy is not activated yet.

Action: Make sure the invoked artifact is correct, deployed correctly and the session used to deploy the artifact is activated without errors.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032002: Received unknown message exchange "{0}" on reply. Reply will be ignored.

Cause: Reply expects message exchange of type "RequestResponseMessageExchange". However, received an unknown message exchange. Hence, reply will be ignored

Action: This is an unexpected error. Please contact support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032003: Neither output nor fault is set on response for message exchange "{0}" for blocking request with key "{1}". Reply will be ignored.

Cause: Either output or fault must be set on a response. However, neither is set for the message exchange.

Action: This is an unexpected error. Please contact support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032004: Callback listener is missing for message exchange "{0}" for non-blocking request with key "{1}". Reply will be ignored.

Cause: Callback listener that is used to dispatch the reply for non-blocking requests is missing. Hence, the reply can not be dispatched.

Action: This is an unexpected error. Please contact support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032005: Neither output nor fault is set on response for message exchange "{0}" for non-blocking request with key "{1}". Reply will be ignored.

Cause: Either output or fault must be set on a response. However, neither is set for the message exchange.

Action: This is an unexpected error. Please contact support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032006: Unknown data type "{2}" found for data in dispatcher cache for request with message exchange "{0}", with key "{1}". Reply will be ignored.

Cause: Type of data found in dispatcher cache is unknown. Hence, reply can not be dispatched.

Action: This is an unexpected error. Please contact support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032007: Timeout for event "{0}" can not be dispatched as the key (used to look up request entry in the dispatcher cache)is null. Timeout will be ignored.

Cause: This error could be due to a system defect in garbage collection or unique id generation. This could also be due to data corruption.

Action: This is an unexpected error. Please contact support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032008: Unknown data type "{0}" found for data, with key "{1}", in the dispatcher cache when trying to dispatch timeout event for a non-blocking request. Timeout will be ignored.

Cause: System defect or data corruption is the cause of this failure.

Action: This is an unexpected error. Please contact support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032009: Error Dispatching the Event: unexpected error. - {0}.

Cause: The exception message should describe the cause.

Action: This is an unexpected error. Please contact support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032010: Error Dispatching the Event: the service-ref is unsupported. - {0}.

Cause: The exception message should describe the cause.

Action: This is an unexpected error. Please contact support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032100: Scheduler can not dispatch request to engine as the process "{0}" is not found. Request will be ignored.

Cause: The process is no longer deployed and active. Either the process is undeployed or session activation failed during process deployed as the session had errors.

Action: Make sure the process is deployed correctly. If error persists, please contact support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032101: Scheduler can not dispatch request to engine for process "{0}" as the message exchange is null. Request will be ignored.

Cause: Message exchange is null.

Action: This is an unexpected error. Please contact support.

Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032400: Failed to acquire lock on {0}.

Cause: An attempt to acquire a lock failed because the object is already locked by another transaction. This generally happens when different threads on the same process instance try to lock the same object. The transaction will be added as blocked to the object and will be locked when the current lock is released.

Action: Nothing. The lock will be acquired when current lock is released.

Level: 1

Type: ERROR

Impact: Other

OSB-2032401: {0} does not own lock on {1}.

Cause: An attempt to unlock an object was made by a transaction that does not own the lock. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

OSB-2032402: There is no current transaction.

Cause: An attempt was made to suspend the current transaction, but there is no current transaction. This should never happen.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other