Uncaught @Async invocations should use BeanExceptionHandler

[lightbody]

This is a feature / enhancement request.

The docs indicate that TaskExceptionHandler can be used to handle uncaught exceptions caused by scheduled tasks, such as methods annotated with @Scheduled. But because @Async can use the same executors, it seems reasonable that those method invocations should also defer exception handling to either TaskExceptionHandler or at least another type of BeanExceptionHandler. Right now AsyncInterceptor catches invocations and simply logs them directly.

Thanks for considering!

[pgrosslicht]

Hi, has this been considered since then? We just ran into this issue as well, we have a custom TaskExceptionHandler to report errors to Sentry and because of this issue errors in @Async methods don't get reported.

[paulolieuthier]

Same here, I was surprised to see there was no error handling for @Async.