thrift
Apache Thrift Exception Codes
Type codes carried by TApplicationException, the exception Apache Thrift RPC clients raise when a call fails at the protocol/framework level rather than with an application-defined exception. Stable across all Thrift language bindings (Java, C++, Python, Go, etc.).
11 codes
references github.com/apache/thrift/blob/master/lib/java/src/main/java/org/apache/thrift/TApplicationException.javadiwakergupta.github.io/thrift-missing-guide/
· All codes 11 codes
- BAD_SEQUENCE_ID Bad Sequence Id The sequence id in the reply did not match the id the client sent with the request, indicating out-of-order or crossed responses on the transport.
- INTERNAL_ERROR Internal Error The server encountered an unhandled error while processing the call, such as an uncaught exception in handler code.
- INVALID_MESSAGE_TYPE Invalid Message Type The message envelope's type field (call, reply, exception, oneway) was not a recognised value.
- INVALID_PROTOCOL Invalid Protocol The client and server negotiated or assumed incompatible protocol implementations.
- INVALID_TRANSFORM Invalid Transform A layered transport transform (such as compression or framing) was invalid or could not be applied to the message.
- MISSING_RESULT Missing Result The reply struct contained neither a success field nor a declared exception field, so the client has no result to return.
- PROTOCOL_ERROR Protocol Error The underlying protocol implementation (binary, compact, JSON, etc.) failed to encode or decode the message.
- UNKNOWN Unknown The RPC failed for an unspecified reason; no more specific TApplicationException type applies.
- UNKNOWN_METHOD Unknown Method The server's processor has no handler registered for the method name the client requested.
- UNSUPPORTED_CLIENT_TYPE Unsupported Client Type The server does not support the type of client that initiated the connection, such as an unsupported transport or protocol negotiation value.
- WRONG_METHOD_NAME Wrong Method Name The method name in the reply envelope did not match the method name the client called; usually indicates mismatched client/server IDL versions.