Skip to content

Commit c0cd55a

Browse files
committed
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
1 parent 35052f2 commit c0cd55a

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

Diff for: framework-docs/modules/ROOT/pages/integration/scheduling.adoc

+4
Original file line numberDiff line numberDiff line change
@@ -475,6 +475,10 @@ seconds, but these values are unused:
475475
----
476476

477477
If the `Publisher` emits an `onError` signal, it is logged at WARN level and recovered.
478+
Because of the asynchronous and lazy nature of `Publisher` instances, exceptions are
479+
not thrown from the Runnable task: this means that the `ErrorHandler` contract is not
480+
involved for Reactive methods.
481+
478482
As a result, further scheduled subscription do happen despite the error.
479483

480484
In the following example, the `Mono` subscription fails twice in the first five seconds

0 commit comments

Comments
 (0)