This is an automated email from the ASF dual-hosted git repository.
Croway pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 8079f1ad8142 camel-sql: docs - point to healthCheckMaxPollDuration
where the page says the consumer health check stays UP during a poll that hangs
8079f1ad8142 is described below
commit 8079f1ad8142db02c6113c8f7c5f6ddd4e2c80ed
Author: croway <[email protected]>
AuthorDate: Mon Nov 16 12:12:52 2026 +0100
camel-sql: docs - point to healthCheckMaxPollDuration where the page says
the consumer health check stays UP during a poll that hangs
---
.../resources/org/apache/camel/catalog/docs/sql-component.adoc | 6 ++++--
components/camel-sql/src/main/docs/sql-component.adoc | 6 ++++--
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sql-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sql-component.adoc
index c8a827131e95..ad7f4eec26e2 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sql-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/sql-component.adoc
@@ -324,8 +324,10 @@ those libraries behave by default; they are approximate,
not guarantees of Camel
connection that went silent (the database host is gone, or a firewall or NAT
dropped the connection without a reset)
waits in a socket read, with no error and nothing logged, until the operating
system gives up on the connection:
on Linux about 15 minutes when the request was not acknowledged, and never
when it was and TCP keep-alive is off.
-Meanwhile the consumer's xref:manual::health-check.adoc[health check] stays
UP, because it counts only the polls that
-failed.
+Meanwhile the consumer's xref:manual::health-check.adoc[health check] stays
UP, because by default it counts only the
+polls that are done. Set `healthCheckMaxPollDuration` (for example
`healthCheckMaxPollDuration=10m`) to have it report
+DOWN while a poll has been running for longer than that: see
+xref:manual::health-check.adoc#_detecting_a_poll_that_hangs[Detecting a poll
that hangs].
A socket timeout ends such a read with an error: the poll fails and is retried
at the next poll, or the producer
fails and the error handler can redeliver. Set it longer than your slowest
statement:
diff --git a/components/camel-sql/src/main/docs/sql-component.adoc
b/components/camel-sql/src/main/docs/sql-component.adoc
index c8a827131e95..ad7f4eec26e2 100644
--- a/components/camel-sql/src/main/docs/sql-component.adoc
+++ b/components/camel-sql/src/main/docs/sql-component.adoc
@@ -324,8 +324,10 @@ those libraries behave by default; they are approximate,
not guarantees of Camel
connection that went silent (the database host is gone, or a firewall or NAT
dropped the connection without a reset)
waits in a socket read, with no error and nothing logged, until the operating
system gives up on the connection:
on Linux about 15 minutes when the request was not acknowledged, and never
when it was and TCP keep-alive is off.
-Meanwhile the consumer's xref:manual::health-check.adoc[health check] stays
UP, because it counts only the polls that
-failed.
+Meanwhile the consumer's xref:manual::health-check.adoc[health check] stays
UP, because by default it counts only the
+polls that are done. Set `healthCheckMaxPollDuration` (for example
`healthCheckMaxPollDuration=10m`) to have it report
+DOWN while a poll has been running for longer than that: see
+xref:manual::health-check.adoc#_detecting_a_poll_that_hangs[Detecting a poll
that hangs].
A socket timeout ends such a read with an error: the poll fails and is retried
at the next poll, or the producer
fails and the error handler can redeliver. Set it longer than your slowest
statement: