Clarify error handling for reactive scheduled methods

This commit adds a note in the reference documentation stating that
`ErrorHandler` infrastructure is not involved when reactive methods send
an error signal: the exception is sent as a message in the pipeline and
is not thrown from the task `Runnable`.

See gh-23533
This commit is contained in:
Brian Clozel 2023-06-05 14:11:39 +02:00
parent 35052f2113
commit c0cd55a8fa
1 changed files with 4 additions and 0 deletions

View File

@ -475,6 +475,10 @@ seconds, but these values are unused:
----
If the `Publisher` emits an `onError` signal, it is logged at WARN level and recovered.
Because of the asynchronous and lazy nature of `Publisher` instances, exceptions are
not thrown from the Runnable task: this means that the `ErrorHandler` contract is not
involved for Reactive methods.
As a result, further scheduled subscription do happen despite the error.
In the following example, the `Mono` subscription fails twice in the first five seconds