Closed joker1007 closed 11 months ago
A reason why I didn't use buildExceptionMessage
is that the method displays only error messages.
I wanted the stack trace of the exception.
I don't think the logging format needs to be aligned with onRetry
.
Because users usually don't need the stack trace of retriable exceptions but typically want the stack trace of not retriable exceptions or given up exceptions.
Got it. Sounds reasonable! Let me merge this.
If a raised exception changes during retry executions and the exception is not retryable, the retrying is aborted instantly, but the information of the last exception is lost, because RetryExecutor throws only the first exception and OnRetry hook doesn't log about the last exception.
For example, like this:
In this situation, it is difficult to identify the root problem, so I would like to change to log also last exception.