Using the Oracle Service Bus Console

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Error Codes

This section describes the Oracle Service Bus errors that can occur when a proxy service is being executed. The error codes associated with these errors surface inside the element of the fault context variable. You can access the value using the following XQuery statement:

$fault/ctx:errorCode/text()

Errors are accompanied by details specific to the error inside the fault element.

Table A-1 lists Oracle Service Bus error codes.

Table A-1 Oracle Service Bus Error Codes 
Subsystem
Error Code
Error Message
Transport Run Time Error
(BEA-380000 to BEA-380099)
BEA-380000
General Transport error
XML Details: An Error Response Was Received
(when occurring in publish action)
Message Flow runtime error codes (382000...382499)
BEA-382000
General runtime error
 
BEA-382030
General parse failure from binding layer (e.g. message to XML service is not XML)
 
BEA-382031
WS-I compliance failure
 
BEA-382032
Message must be a soap:Envelope
XML Details: A Non-SOAP or Invalid Envelope Was Received
 
BEA-382033
A soap:Envelope must contain a soap:Body
 
BEA-382040
Failed to assign value to context variable "{0}". Value must be an instance of {1}
 
BEA-382041
Failed to assign value to context variable "{0}". Variable is read-only.
 
BEA-382042
Failed to assign value to context variable "{0}". {1}
 
BEA-382043
Failed to update the value of context variable "{0}": {1}
 
BEA-382045
Failed to initialize the value of context variable "{0}": {1}
 
BEA-382046
Failed to marshall the value of context variable "{0}" to XML: {1}
 
BEA-382100
General binding error while processing inbound request
 
BEA-382101
General binding error while preparing inbound response
 
BEA-382102
General binding error while preparing outbound request
 
BEA-382103
General binding error while processing outbound response
 
BEA-382104
Failed to prepare request metadata for service {0}
 
BEA-382105
Failed to prepare response metadata for service {0}
 
BEA-382150
Failed to dispatch request to service {0}
 
BEA-382151
Cannot dispatch to unknown service: {0}
Action error codes (382500...382999)
BEA-382500
ALSBConfigurationMBean service callout action received SOAP Fault response.
XML details: A SOAP Fault Response was Received
 
BEA-382501
Oracle Service Bus service callout action received an unrecognized response. XML details: An Unrecognized Response was Received
 
BEA-382502
Oracle Service Bus service callout has received an error response from the server XML details: An Unknown Error Response Was Received
 
BEA-382505
Oracle Service Bus Validate action validation failed.
XML details: Validation Failed
 
BEA-382510
Oracle Service Bus Assign action failed updating variable "{0}": {1}
 
BEA-382511
Oracle Service Bus Delete action failed updating variable "{0}": {1}
 
BEA-382512
Oracle Service Bus Insert action failed updating variable "{0}": {1}
 
BEA-382513
Oracle Service Bus Replace action failed updating variable "{0}": {1}
 
BEA-382514
Oracle Service Bus Rename action failed updating variable "{0}": {1}
 
BEA-382515
Callout to java method "{0}" resulted in exception: {1}
 
BEA-382516
Failed to evaluate expression for callout to java method "{0}". Argument index: {1}, exception: {2}
 
BEA-382517
Failed to assign the result of Java callout to variable. Method: {0}, variable: {1}, exception: {2}
 
BEA-382518
Security exception while calling to java method "{0}". Service account: {1}. {2}
 
BEA-382600
Oracle Service Bus publish action received an error response: {0}
Security error codes (386000...386999)
BEA-386000
General security error. Possible reasons include the following:
  • Custom token or custom user name/password authentication is configured but authentication already took place via WS-Security.
 
BEA-386100
Authentication failed. Possible reasons include the following:
  • The XPath is configured to act on the body or header but there is no such message part (the binding layer returns null).
  • The XPath engine throws an exception when evaluating the XPath expression.
  • The result of the user name XPath or password XPath is a node that is not of type TEXT or ATTR.
  • The XPath returns more than one node.
  • A user name/password was retrieved but authentication failed.
  • A custom token was retrieved but identity assertion failed (the CSS identity assertion service throws LoginException or any other exception).
 
BEA-386101
Missing authentication token. Possible reasons include the following:
  • The user name XPath or password XPath returns an empty result or empty string.
  • The custom token XPath returns an empty result, null attribute value, or null text-value.
 
BEA-386102
Message-level authorization denied. Possible reasons include the following:
  • The message level access control policy denies access to the proxy service.
 
BEA-386103
The proxy service operation selection algorithm cannot determine the operation name from the request or returns an invalid operation (one which is not in the WSDL or null). Possible reasons include the following:
  • An error occurs while computing the operation.
  • The operation selection algorithm returns null.
  • The operation selection algorithm returns an operation that is not of the of the operations declared by the WSDL.
 
BEA-386200
General web service security error
 
BEA-386201
A web service security fault occurred[<error-code from WSS fault>][<fault-string from WSS-fault>] XML details: A WS-Security Fault Occurred
 
BEA-386400
General outbound web service security error
 
BEA-386401
Failed to convert outbound message to SOAP
 
BEA-386402
Cannot determine the outbound operation
 
BEA-386420
A web service security error occurred while producing security header
 
BEA-386440
A web service security error occurred while processing the security header
 
BEA-386460
Web Service Security policy validation error
UDDI error codes (394500...394999)
BEA-394500
An error was encountered while importing a resource
 
BEA-394501
An error was encountered while querying the UDDI registry for business entities
 
BEA-394502
An error was encountered while initializing the UDDI service
 
BEA-394503
An error was encountered while initializing the inquiry port
 
BEA-394504
An error was encountered while publishing this service
 
BEA-394505
Failed to connect to the UDDI registry
 
BEA-394506
An error was encountered while querying the UDDI registry for business services
 
BEA-394507
The registry name contains characters that are not allowed
 
BEA-394508
The publish URL was missing the UDDI registry configuration
 
BEA-394509
The Service Account configured is not valid
 
BEA-394510
A resource could not imported while importing a service
 
BEA-394511
A validation exception occurred while creating a service definition while importing a service
 
BEA-394512
A generic error was encountered while importing a resource
 
BEA-394513
An internal error was encountered while importing a resource
 
BEA-394514
Failed to create an FTP endpoint configuration when importing a service
 
BEA-394515
Failed to create an E-mail endpoint configuration when importing a service
 
BEA-394516
A possible syntax error was encountered in the access point URL when importing a service
 
BEA-394517
An error was encountered when parsing the InstanceParms while importing a service
 
BEA-394518
Failed to create an file endpoint configuration when importing a service

 

Error Details Schemas

Below are schema definitions for XML snippets that accompany the error codes listed in Table A-1. These XML snippets appear inside the fault context variable under the <ctx:details> element. These schemas do not all come from a single namespace. Also, while a given error code typically implies a particular XML snippet, some XML snippets are used by several error codes. 

<xs:schema targetNamespace="http://www.oracle.com/wli/sb/stages/transform/config"
           xmlns:tns="http://www.oracle.com/wli/sb/stages/transform/config"
	   xmlns:xs="http://www.w3.org/2001/XMLSchema"
           xmlns:ref="http://www.oracle.com/wli/sb/reference"
           xmlns:sdk="http://www.oracle.com/wli/sb/stages/config"
	   elementFormDefault="qualified"
	   attributeFormDefault="unqualified">

A SOAP Fault Response was Received 

    <xs:element name="ReceivedFaultDetail" type="tns:ReceivedFaultDetail"/>
    <xs:complexType name="ReceivedFaultDetail">
        <xs:sequence>
            <xs:element name="faultcode" type="xs:QName"/>
            <xs:element name="faultstring" type="xs:string"/>
            <xs:element name="detail" minOccurs="0" >
                <xs:complexType mixed="true" >
                    <xs:sequence>
                        <xs:any namespace="##any" minOccurs="0" maxOccurs="unbounded" processContents="lax" />
                    </xs:sequence>
                    <xs:anyAttribute namespace="##any" processContents="lax" />
                </xs:complexType>
            </xs:element>
            <!-- HTTP-specific status/response code -->
            <xs:element name="http-response-code" type="xs:int" minOccurs="0"/>
        </xs:sequence>
    </xs:complexType>

An Unrecognized Response was Received 

    <xs:element name="UnrecognizedResponseDetail" type="tns:UnrecognizedResponseDetail"/>
    <xs:complexType name="UnrecognizedResponseDetail">
        <xs:sequence>
            <xs:element name="detail" minOccurs="0" type="xs:string" />
            <!-- HTTP-specific status/response code -->
            <xs:element name="http-response-code" type="xs:int" minOccurs="0"/>
        </xs:sequence>
    </xs:complexType>

An Unknown Error Response Was Received 

    <xs:element name="ErrorResponseDetail" type="tns:ErrorResponseDetail"/>
    <xs:complexType name="ErrorResponseDetail">
        <xs:sequence>
            <xs:element name="detail" minOccurs="0" type="xs:string" />
            <!-- HTTP-specific status/response code -->
            <xs:element name="http-response-code" type="xs:int" minOccurs="0"/>
        </xs:sequence>
    </xs:complexType>

Validation Failed 

    <xs:complexType name="ValidationFailureDetail">
        <xs:sequence minOccurs = "0" maxOccurs="unbounded">
            <xs:element name="message" type="xs:string"/>
            <xs:element name="xmlLocation" type="xs:anyType"/>
        </xs:sequence>
    </xs:complexType>
</xs:schema>
<schema targetNamespace="http://www.oracle.com/wli/sb/errors"
        xmlns:err="http://www.oracle.com/wli/sb/errors"
        xmlns:tc="http://www.oracle.com/wli/sb/transports"
        xmlns="http://www.w3.org/2001/XMLSchema"
        elementFormDefault="qualified"
        attributeFormDefault="unqualified">

A Non-SOAP or Invalid Envelope Was Received 

    <element name="InvalidEnvelope">
        <complexType>
            <sequence>
                <element name="localpart" type="NCName"/>
                <element name="namespace" type="anyURI" minOccurs="0"/>
            </sequence>
        </complexType>
    </element>

A WS-Security Fault Occurred 

    <element name="WebServiceSecurityFault">
        <complexType>
            <sequence>
                <element name="faultcode" type="QName"/>
                <element name="faultstring" type="string"/>
                <element name="detail" minOccurs="0">
                    <complexType mixed="true">
                        <sequence>
                            <any namespace="##any" minOccurs="0" maxOccurs="unbounded" processContents="lax"/>
                        </sequence>
                        <anyAttribute namespace="##any" processContents="lax"/>
                    </complexType>
                </element>
            </sequence>
        </complexType>
    </element>

An Error Response Was Received 

    <element name="ErrorResponseDetail" type="err:ErrorResponseDetail"/>
    <complexType name="ErrorResponseDetail">
        <sequence>
            <!-- Response metadata -->
            <element name="response-metadata" type="tc:ResponseMetaDataXML" minOccurs="0" />
        </sequence>
    </complexType>
</schema>

  Back to Top       Previous  Next