tencent cloud



Last updated: 2024-02-29 17:31:27


    When calling the SDK to request the COS or CI service fails, all exceptions reported are RuntimeExcpetion. Common exceptions in the SDK currently include CosClientException, CosServiceException, CIServiceException, and IllegalArgumentException.

    Client Exceptions

    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 RuntimeException, CosClientException has no custom member variables, and is used in the same way as RuntimeException.

    Server Exceptions

    CosServiceException and CIServiceException refer to scenarios where the interaction is completed 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 the operation, or the server fails. CosServiceException contains the status code, request ID, and error details. After such an exception is captured, we recommend you print out the entire exception as it contains necessary factors for troubleshooting. The following describes the member variables of the exception:
    Request Element
    Request ID, which is used to identify a request and is very important for troubleshooting.
    ID for troubleshooting
    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.
    Enumeration type, indicating the type of exception, such as Client, Service, and Unknown.
    Error code returned by the body when the request fails. For more information, see Error Codes.
    Error message returned by the body when the request fails. For more information, see Error Codes.

    Using the Diagnosis Tool

    CI provides a self-help diagnosis tool to help you quickly locate request errors and debug the code.


    1. Copy the request ID (RequestId) returned when the request error occurs.
    2. Click Diagnosis Tool.
    3. Enter RequestId and click Diagnose.
    4. Wait and view the diagnostic result.


    If you have any questions about the Java SDK, see FAQs.
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support