Overview

If a COS request fails when calling this SDK, it will throw a CosXmlClientException (client exception) or CosXmlServiceException (server exception).

• The client exception, CosXmlClientException, 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.
• The server exception, CosXmlServiceException, 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.

Client Exceptions

Inherited from Exception, CosClientException is used in the same way as Exception. An additional member errorCode is also added, as described below:

Server Exceptions

The server exception, CosXmlServiceException, occurs when, 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. CosXmlServiceException 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:

Using the Diagnosis Tool

COS provides a self-help diagnosis tool to help you quickly locate request problems and debug code.

Directions

1. Copy the request ID (RequestId) returned when the request error occurs.
2. Click Diagnosis Tool.
   Diagnosis Tool

   Click to start diagnosis

   Enter `RequestId` for intelligent diagnosis and obtain basic request information, directions, and diagnosis information to quickly locate request errors.
3. Enter RequestId and click Diagnose.
4. Wait and view the diagnostic result.