Page Comparison

...

Given below are some error codes and their meanings.

API handlers error codes

...

700700

900800

900801

900900

900901

900902

900905

900906

900907

900908

900909

900910

...

...

Sequences error codes

900901

400

403

In addition to the above error codes, we have engaged Synapse-level error codes to the default fault sequence and custom fault sequences (e.g.,_token_fault_.xml) of the API Manager. For information, see Error Handling in WSO2 ESB documentation.

Transport error codes

If the HTTP PassThrough transport is used, and a connection-level error occurs, the error code is calculated using the following equation:

There is a machine state in the transport sender side, where the protocol state changes according to the phase of the message.

Following are the possible protocol states and the description for each:

Since there are several possible protocol states in which a request can time out, you can calculate the error code accordingly using the values in the table above. For example, in a scenario where you send a request and the request is completely sent to the backend, but a timeout happens before the response headers are received, the error code is calculated as follows:

In this scenario, the base error code is CONNECTION_TIMEOUT(101504) and the protocol state is REQUEST_DONE(3).

Therefore, 

Error code = 101504 + 3 = 101507

These Transport error codes are used in Advanced Configurations of Endpoints.

Custom error messages

To send a custom message with a custom HTTP status code, you execute an additional sequence that can generate a new error message. You then override the message body, HTTP status code and other values.

...

1. Go to <APIM_HOME> /repository/deployment/server/synapse-configs/default/sequences directory and create the file convert.xml as follows.

   Code Block
   language xml
   <sequence xmlns="http://ws.apache.org/ns/synapse" name="convert"> <payloadFactory media-type="xml"> <format> <am:fault xmlns:am="http://wso2.org/apimanager"> <am:code>$1</am:code> <am:type>Status report</am:type> <am:message>Runtime Error</am:message> <am:description>$2</am:description> </am:fault> </format> <args> <arg evaluator="xml" expression="$ctx:ERROR_CODE"/> <arg evaluator="xml" expression="$ctx:ERROR_MESSAGE"/> </args> </payloadFactory> <property name="RESPONSE" value="true"/> <header name="To" action="remove"/> <property name="HTTP_SC" value="555" scope="axis2"/> <property name="NO_ENTITY_BODY" scope="axis2" action="remove"/> <property name="ContentType" scope="axis2" action="remove"/> <property name="Authorization" scope="transport" action="remove"/> <property name="Access-Control-Allow-Origin" value="*" scope="transport"/> <property name="Host" scope="transport" action="remove"/> <property name="Accept" scope="transport" action="remove"/> <property name="X-JWT-Assertion" scope="transport" action="remove"/> <property name="messageType" value="application/json" scope="axis2"/> <send/> </sequence>

   Tip
   Alternatively, you can use the Source View of the APIm Management Console as follows to edit the synapse configuration: Start the API Manager and log in to the Management Console. (https://<Server Host>:9443/carbon). Go to Manager > Source View. Copy the content of the sequence in convert.xml, paste it as a new sequence in the source view and update it.

2. Check the logs to see whether there are issues in the deployment.  If the deployment is successful, you see a message like the following in the system logs:

   Background Color
   color default
   [2015-04-13 09:17:38,885]  INFO - SequenceDeployer Sequence named 'convert' has been deployed from file : <APIM_HOME>/repository/deployment/server/synapse-configs/default/sequences/convert.xml

3. Invoke the API until the throttling limit exceeds and the new requests get throttled out. 

   Code Block
   curl -v -H "Authorization: Bearer <Access_Token>" http://localhost:8280/<API_name>/<context>/<version>

4. Note that you get following response:

   Code Block
   language xml
   * About to connect() to 127.0.0.1 port 8280 (#0) * Trying 127.0.0.1... * Adding handle: conn: 0x17a2db0 * Adding handle: send: 0 * Adding handle: recv: 0 * Curl_addHandleToPipeline: length: 1 * - Conn 0 (0x17a2db0) send_pipe: 1, recv_pipe: 0 * Connected to 127.0.0.1 (127.0.0.1) port 8280 (#0) > GET /testam/sanjeewa/1.0.0 HTTP/1.1 > User-Agent: curl/7.32.0 > Host: 127.0.0.1:8280 > Accept: */* > Authorization: Bearer 7f855a7d70aed820a78367c362385c86 > < HTTP/1.1 555 < Access-Control-Allow-Origin: * < Content-Type: application/json < Date: Mon, 13 Apr 2015 05:30:12 GMT * Server WSO2-PassThrough-HTTP is not blacklisted < Server: WSO2-PassThrough-HTTP < Transfer-Encoding: chunked < * Connection #0 to host 127.0.0.1 left intact {"fault":{"code":"900800","type":"Status report","message":"Runtime Error","description":"Message throttled out"}}

WSO2 API Manager has the following default fault sequences located in <APIM_HOME> /repository/deployment/server/synapse-configs/default/sequences directory.