allthingssecurity commented on PR #28204: URL: https://github.com/apache/camel/pull/28204#issuecomment-6314804372
Thanks Andrea. 1. Confirmed in jnats 2.26.4: `lookupConsumerInfo` maps 10014 to null, so `consumerGone` now treats null as gone, and the fake answers like jnats (null for a deleted consumer, the info for a live one); with that fake the previous commit no longer recovers. 2. `subscribeAgain` looks the stream up first: on a WorkQueue stream it uses the configuration as is, and when the create time differs from the one seen at the subscribe it clears the tracked sequences and uses the configuration as is. The fake now models both, with a test each. 3. The check runs only after an empty fetch that ended before half of `pullFetchTimeout`, so an idle healthy consumer sends no CONSUMER.INFO; other error statuses now wait for the rest of the fetch timeout. 4. With AckPolicy.None nothing is tracked, the new consumer starts after the highest fetched sequence. 5. Both use `setResultWaitTime(20_000)` now. I also added `NatsJetstreamConsumerPullDeletedIT`, which deletes the consumer with `jsm.deleteConsumer` while the route is busy; I could not run it here (no Docker), CI will (f946daeb27ce). _Claude Code on behalf of allthingssecurity_ -- 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]
