Bug
Important information not logged
Issue description
Under certain circumstances only a fragment of the stack trace is logged and the important last callers are not present, giving only the generic request processing part and omitting the specifics.
Developer comments
In all instances a technical exception was caught and replaced by a ClientException. Even though the ClientException can be connected with a cause, this mechanism was not used. The issue was resolved by allowing the first argument of the ClientException to be an Exception of which is the caused then. All the important information is thus logged now.
|
Work sessions
Start |
2020-05-20T07:43:47
|
End |
2020-05-20T08:33:58
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.