Release Notes
Announcements
RuntimeExcpetion.
Common exceptions in the SDK currently include CosClientException, CosServiceException, CIServiceException, and IllegalArgumentException.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.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 | Description | Type |
requestId | Request ID, which is used to identify a request and 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, such as Client, Service, and Unknown. | ErrorType |
errorCode | String | |
errorMessage | String |
RequestId) returned when the request error occurs.RequestId and click Diagnose.Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan