...
| Section | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Introduction
Errors may occur in many different situations during the data processing. yuuvis® Momentum core offers a well-defined structure and labeling and of any thrown error. It is thus possible to easily localize the origin of the problem. At the same time, automated catching and analyzing of errors can be implemented based on the fixed error structure and error codes.
Error Structure
The errors are JSON structures with the following parameters:
| Parameter | Description |
|---|---|
httpStatusCode | Three-digit Integer specifying the type of errorHTTP status code as a class of the response in which the error is returned. |
serviceErrorCode | Four-digit Integer specifying the concrete error type. |
time | Timestamp of the error occurance in format "yyyy-MM-ddTHH:mm:ss.SSS". |
message | String message describing the concrete error. |
stackTrace | Origin of the error. |
service | The name of the service that throwed the error. |
tenant | The string tenant name where the error occured. |
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"httpStatusCode" : 409,
"serviceErrorCode" : 2800,
"time" : "2021-04-21T04:36:30.813",
"message" : "A non-empty folder cannot be deleted.",
"stackTrace" : [ "com.os.enaio.cloud.gateway.resource.api.DmsController.deleteDmsObject(DmsController.java:719)" ],
"service" : "api",
"tenant" : "default"
} |
...
Note: In case you want to catch errors and analyse their content, please use the serviceErrorCode as unique identification of the error type. Please do NOT use the message since we reserve to modify it in future.
...