etzel-mes commented on code in PR #28219:
URL: https://github.com/apache/camel/pull/28219#discussion_r4335807200
##########
docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_24.adoc:
##########
@@ -2075,6 +2075,14 @@ To keep the previous behaviour, filter the exchanges
with a bad status out right
`filter(simple("${body.statusCode.bad} == false"))`. This also drops the other
bad statuses, such as the refusal of a
node, and the current values delivered after an outage still arrive.
+=== camel-milo - the reconnectTimeout of the components sets the delay between
connection attempts
+
+`setReconnectTimeout` on the `milo-client` and `milo-browse` components set
the request timeout of every service call,
+and the delay between two connection attempts stayed 10 seconds. It now sets
that delay, which the new
+`reconnectTimeout` option of both endpoints and components sets too; its
default of 10000 milliseconds is the previous
+delay, and a value of 0 or less is rejected. A component that called
`setReconnectTimeout` to set the request timeout
+uses `setRequestTimeout` for it.
Review Comment:
Thanks, you are right: the components have no `setRequestTimeout` of their
own. Applied your wording in e3716c0018c.
_Claude Code on behalf of etzel-mes_
--
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]
