Whenever a COS request fails when calling this SDK, the system throws a
RuntimeExcpetion. Common SDK exceptions are
The client exception,
CosClientException, results from unexpected interaction issues between the client and the COS server, such as a failure to connect to the server, a failure to parse the data returned by the server, or the occurrence of an IO exception when reading a local file. Inherited from
CosClientException has no custom member variables, and is used in the same way as
The server exception,
CosServerException, occurs when the client interacts with the COS server normally, but the operation fails. For example, the client accesses a bucket that does not exist, deletes a file that does not exist, or does not have the permission to perform an operation, etc.
CosServiceException contains the status code returned by the server, the
requestid, the error details, and so on. After an exception is captured, we recommended that you print out the entire exception as it contains necessary factors for troubleshooting. The member variables of exception are described as follows:
|requestId||Request ID, used to identify a request. It is very important for troubleshooting.||String|
|traceId||ID for troubleshooting||String|
|statusCode||Status code in the response. 4xx indicates that the request failed due to a client exception. 5xx indicates that the request failed due to a server exception. For more information, see Error Codes.||String|
|errorType||Enumeration type, indicating the type of exception, e.g.,
|errorCode||Error code returned by the body when the request fails. For more information, see Error Codes.||String|
|errorMessage||Error message returned by the body when the request fails. For more information, see Error Codes.||String|
COS provides a self-help diagnosis tool to help you quickly locate request problems and debug code.
RequestId) returned when the request error occurs.
RequestIdand click Diagnose.
If you have any questions about Java SDK, see the Java SDK section in FAQs.