...
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 |
101000 | Receiver input/output error sending |
101001 | Receiver input/output error receiving |
101500 | Sender input/output error sending |
101501 | Sender input/output error receiving |
101503 | Connection failed |
101504 | Connection timed out |
101505 | Connection closed |
101506 | NHTTP protocol violation |
101507 | Connection canceled |
101508 | Connection timed out |
101509 | Send abort |
101510 | Response 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 Code | Detail |
303000 | Load Balance endpoint is not ready to connect |
303000 | Recipient List Endpoint is not ready |
303000 | Failover endpoint is not ready to connect |
303001 | Address Endpoint is not Ready to connect |
303002 | WSDL Address is not ready to connect |
Failure on Endpoint in the Session
Error Code | Detail |
309001 | Session aware load balance endpoint, No ready child endpoints |
309002 | Session aware load balance endpoint, Invalid reference |
309003 | Session aware load balance endpoint, Failed session |
Non-Fatal Warnings
Error Code | Detail |
303100 | A failover occurred in a Load balance endpoint |
304100 | A failover occurred in a Failover endpoint |
Referring Real Endpoint is Null
Error Code | Detail |
305100 | Indirect endpoint not ready |
Callout Operation Failed
Error Code | Detail |
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. |