Croway opened a new pull request, #30065: URL: https://github.com/apache/camel/pull/30065
Docs only. The page had nothing on publisher confirms, heartbeats or channel timeouts. Fault-injection tests (a silently dropped connection and a reset in front of a real RabbitMQ) showed a producer without publisher confirms reporting success for messages that were lost, a consumer that noticed nothing during a 35-second outage, and duplicates after a reconnect. **spring-rabbitmq-component.adoc**: new section "Noticing a dead or silent broker", after "Using a connection factory": - publisher confirms: without them a send on a silent or reset connection succeeds and the message can be lost; with simple publisher confirms the default `confirm=auto` waits up to `confirmTimeout` (5 s) and fails the send, so the error handler can redeliver (relies on CAMEL-25947, already on `main`); - heartbeat: 60 s by default, the client reads with a timeout of a quarter of it and closes the connection after more than 8 timeouts in a row, about 2.25 × heartbeat (about 135 s); - `channelRpcTimeout` (10 min) for channel RPCs such as opening a channel or cancelling a consumer; - examples for a `CachingConnectionFactory` bean and Spring Boot properties; - duplicates up to `prefetchCount` after a reconnect. The auto-declare section is not touched. Checked against the sources at the versions on `main`: Spring AMQP 4.1.2 (`CachingConnectionFactory`, `AbstractConnectionFactory`, `AbstractMessageListenerContainer`), RabbitMQ Java client 5.31.0, the version Spring AMQP 4.1.2 uses (`AMQConnection.handleSocketTimeout` / heartbeat negotiation, `ConnectionFactory` defaults, `ChannelN.waitForConfirms`, `AMQChannel` RPC timeout, `ConsumerDispatcher` shutdown ordering), Spring Boot 4.0.9 `RabbitProperties`, and Camel's `SpringRabbitMQProducer`, `SpringRabbitMQEndpoint` and `SpringRabbitMQComponent`. The durations are given as approximate behaviour of the client libraries. The catalog copy is regenerated. _Claude Code on behalf of Croway_ -- 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]
