davsclaus opened a new pull request, #25632: URL: https://github.com/apache/camel/pull/25632
## Backport of #25630 Cherry-pick of #25630 onto `camel-4.22.x`. **Original PR:** #25630 - chore: fix NATS JetStream IT tests sharing a stream/durable name **Original author:** @davsclaus **Target branch:** `camel-4.22.x` Verified this branch has the same collision as `main` had before the fix: `NatsJetstreamConsumerAckPolicyNoneIT`, `NatsJetstreamConsumerMaxDeliverIT`, and `NatsJetstreamConsumerRedeliveryIT` share the same JetStream stream name (`mystream2`), subject (`mytopic2`), and durable consumer name (`camel2`), with no `@DisabledIfSystemProperty` guard on this branch to mask it. ### Original description - `NatsJetstreamConsumerAckPolicyNoneIT`, `NatsJetstreamConsumerMaxDeliverIT`, and `NatsJetstreamConsumerRedeliveryIT` all used the identical JetStream stream name (`mystream2`), subject (`mytopic2`), and durable consumer name (`camel2`). - `NatsITSupport` doesn't tear down streams/consumers between IT classes, and `NatsConsumer.setupJetStreamConsumer()` never reconciles an already-existing durable consumer's config with a new subscribe request. Whichever of these three tests ran first bound its own `ackPolicy`/`maxDeliver` config to the shared durable consumer server-side; the next test(s) in the suite then silently bound to that stale, mismatched consumer and received zero messages. - Fix: give each test its own unique stream/subject/durable name (`-ackpolicynone`, `-maxdeliver`, `-redelivery` suffixes), matching the convention already used correctly by the other JetStream IT tests in this package. Test-only change, no production code touched. --- _Claude Code on behalf of davsclaus_ -- 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]
