Using the AquaLogic Service Bus Console
Error Codes
This section describes the AquaLogic 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 B-1 AquaLogic Service Bus Error Codes
Subsystem
|
Error Code Range
|
Details
|
Transport Run Time
|
BEA-380000—BEA-380999
|
General transport error
|
Proxy Service Run Time
|
BEA-382000—BEA-382499
|
General runtime error
General parse failure from binding layer (e.g. message to
XML service is not XML)
WS-I compliance failure
Message must be a soap:Envelope
A soap:Envelope must contain a soap:Body
Failed to assign value to context variable "{0}". Value must
be an instance of {1}
Failed to assign value to context variable "{0}". Variable is
read-only
General binding error while processing inbound request
General binding error while preparing inbound response
General binding error while preparing outbound request
General binding error while processing outbound response
Failed to prepare request metadata for service {0}
Failed to prepare response metadata for service {0}
Failed to dispatch request to service {0}
Cannot dispatch to unknown service: {0}
|
Actions
|
BEA-382500—BEA-382999
|
Service callout action received SOAP Fault response
Service callout action received an unrecognized response
Service callout has received an error response from the
server
Validate action validation failed
|
Security
|
BEA-386000—BEA-386999
|
General security error
General web service security error
General outbound web service security error
Failed to convert outbound message to SOAP
Cannot determine the outbound operation
A web service security error occurred while producing
security header
A web service security error occurred while processing the
security header
Web service security policy validation error
|
UDDI
|
BEA-394500—BEA-394999
|
An error was encountered while importing a resource
An error was encountered while querying the UDDI registry
for business entities
An error was encountered while initializing the UDDI
service
An error was encountered while initializing the inquiry port
An error was encountered while publishing this service
Failed to connect to the UDDI registry
An error was encountered while querying the UDDI registry
for business services
The registry name contains characters that are not allowed
The publish URL was missing the UDDI registry
configuration
The Service Account configured is not valid
A resource could not imported while importing a service
|
|
|
A validation exception occurred while creating a service
definition while importing a service
A generic error was encountered while importing a resource
An internal error was encountered while importing a
resource
Failed to create an FTP endpoint configuration when
importing a service
Failed to create an e-mail endpoint configuration when
importing a service
A possible syntax error was encountered in the access point
URL when importing a service
An error was encountered when parsing the InstanceParms
while importing a service
Failed to create a file endpoint configuration when
importing a service
|