You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@smaldini Rethrowing here would make sense if WorkerTask used UncaughtExceptionHandler but it doesn't so this needs to be done here, and I see no reason at all why any specific, JVM or other error types, should result in UncaughtExceptionHandler not being used, especially given these errors are not propagated via onErrror.
I also am not sure why onHandleErrorHook should not be notified of these fatal exceptions. Given these errors will not be propagated up, there is no way for the user to handle these errors and perform any logging/cleanup otherwise.
The fatal exceptions will probably be thrown down the line and they are
still considered irrecoverable, but when they happen within a Thread
from a Scheduler, they should be passed to the handleError hook
as well as to the Thread's uncaughtExceptionHandler if any.
Such a sequence may hang, as the test demonstrates, but the fatal error
has a chance to be logged.
Expected behavior
Error logged.
Actual behavior
Silent failure and pipeline does not complete.
Steps to reproduce
Reactor Core version
3.0.4-RELEASE
JVM version (e.g.
java -version
)1.8
OS version (e.g.
uname -a
)Ubuntu 16.04
The text was updated successfully, but these errors were encountered: