Croway opened a new pull request, #30265:
URL: https://github.com/apache/camel/pull/30265

   ## Summary
   
   Follow-up of #30162 
([CAMEL-27013](https://issues.apache.org/jira/browse/CAMEL-27013)). That fix 
documented the new behaviour on the SQL component page, but not in the upgrade 
guide. It is a bug fix, yet it changes what a user observes on upgrade:
   
   - on the instance that holds a key (added, not confirmed or removed yet), 
`contains` returns true and `add` returns false whatever the age of its 
`createdAt`; before, that instance took its own key over once the lease was 
older than `lockMaxAgeMillis`;
   - the keep-alive logs a WARN when it has not refreshed the leases of the 
instance for longer than `lockMaxAgeMillis`, and an INFO when it refreshes them 
again;
   - code that ages the `createdAt` of a key and expects the repository that 
added it to see it as absent no longer works. This broke 
`JdbcOrphanLockAwareIdempotentRepositoryTest` in `camel-sql-starter` (fixed in 
apache/camel-spring-boot#2105).
   
   This adds a short `camel-sql` section to the 4.24 upgrade guide, right after 
the one about confirmed keys (CAMEL-26816). It also repeats that another 
instance still takes such a key over, so `lockMaxAgeMillis` must be longer than 
the longest database outage to survive. Docs only.
   
   _Claude Code (Fable 5.2) on behalf of Federico Mariani_
   


-- 
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