davsclaus commented on code in PR #29896:
URL: https://github.com/apache/camel/pull/29896#discussion_r4583963045


##########
docs/user-manual/modules/ROOT/pages/error-handler.adoc:
##########
@@ -211,7 +211,11 @@ resource is released as failed
 |A `VirtualMachineError`, such as `OutOfMemoryError`, `StackOverflowError` or 
`InternalError`
 |Camel's error handling does not get it (the JVM may no longer be in a 
consistent state, so the application should not
 handle it). It is not set on the exchange, but thrown on after the processor's
-callback was called. Depending on the error handler, the `Error` reaches the 
caller (and the exchange may stay
+callback was called (a `VirtualMachineError` of an `AggregationStrategy` or of 
the iterator of a split is thrown on
+from the task of the EIP, and the callback is not called unless the EIP is 
`synchronous=true` or the exchange is transacted, in both
+cases without `parallelProcessing`; with `parallelProcessing`, or from the 
`timeout` of the strategy, it is lost on a
+thread of the pool).

Review Comment:
   Done in 5d20c5ef82a9: the long bracketed text is now three sentences. One 
says what happens to a `VirtualMachineError` of a strategy or split iterator, 
one says when the callback is still called (`synchronous=true` or transacted, 
without `parallelProcessing`), and one covers `parallelProcessing` and the 
strategy `timeout`.
   
   _Claude Code on behalf of davsclaus_



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to