This page describes HTTP response codes sent by the resource adaptor in server mode, and response codes used in artificial response events generated in client mode.
Acting as a server
The resource adaptor sends the following response codes to clients when there are event processing errors:
| Code | Message | Reason |
|---|---|---|
|
"Server Too Busy" |
Activity could not be started due to non system-level issues such as an input rate limiting policy. |
|
"Internal Server Error" |
Activity could not be started due to non system-level or any other issues. |
|
"Server Error" |
Resource adaptor event processing failed. |
|
"Not Implemented" |
Event filtered by an |
The resource adaptor also sends the following response codes to clients in the cases described:
| Code | Message | Reason |
|---|---|---|
|
"Missing Host Header" |
Host header not set for HTTP v1.1 request. |
|
"Not found" |
Host and URI constitute a malformed URL. |
Acting as a client
In certain scenarios when operating in client mode, the resource adaptor will fire response events when no response has been received from the server.
|
The HttpResponse.isServerResponse()
method allows a service to distinguish between responses received from the remote server and responses generated by the resource adaptor.
|
| Code | Message | Reason |
|---|---|---|
|
"Server closed connection" |
Connection closed by a remote server. |
|
"Read error: <cause>" |
Failure on receiving response in client. |
|
"Write error: <cause>" |
Failure on sending request from client. |
|
"Timed out waiting for server connection" |
Queue timeout met before a connection was available and the request could be sent. |
|
"RA deactivation while waiting for server connection" |
The resource adaptor reactivated before a connection was available and the request could be sent. |
