Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note how the ERROR_MESSAGE property is being used to get the error message text. If you want to customize the error message that is sent back to the client, you can use the makefault mediator as demonstrated in Sample 5: Creating SOAP Fault Messages and Changing the Direction of a Message.

Transport Error Codes

 

Error Code Detail
101000Receiver input/output error sending
101001Receiver input/output error receiving
101500Sender input/output error sending
101501Sender input/output error receiving
101503Connection failed
101504Connection timed out
101505Connection closed
101506NHTTP protocol violation
101507

Connection canceled

101508Connection timed out
101509Send abort
101510Response processing failed

Endpoint Failures

This section describes the error codes for endpoint failures. For more information on handling endpoint errors, see Endpoint Error Handling.

General Errors

 

Error CodeDetail
303000Load Balance endpoint is not ready to connect
303000Recipient List Endpoint is not ready
303000Failover endpoint is not ready to connect
303001Address Endpoint is not Ready to connect
303002WSDL Address is not ready to connect

Failure on Endpoint in the Session

 

Error CodeDetail
309001Session aware load balance endpoint, No ready child endpoints
309002Session aware load balance endpoint, Invalid reference
309003Session aware load balance endpoint, Failed session

Non-Fatal Warnings

 

Error CodeDetail
303100A failover occurred in a Load balance endpoint
304100A failover occurred in a Failover endpoint

Referring Real Endpoint is Null

 

Error CodeDetail
305100Indirect endpoint not ready

Callout Operation Failed

 

Error CodeDetail
401000 Callout operation failed (from the callout mediator)

Info

For information on best practices for handling errors in WSO2 ESB, see WSO2 ESB by Example - Best practices for error handling on the WSO2 ESB.