anvithsg2004 commented on PR #23902: URL: https://github.com/apache/camel/pull/23902#issuecomment-4668348259
The JDK 17 job failure is unrelated to this change — the failing test is `PulsarConsumerNoAcknowledgementIT#testAMessageIsConsumedMultipleTimesWithAckTimeoutBackoff`, while this PR only touches `PulsarSharedSubscriptionMessageDistributionIT` (different topic and subscription). It looks pre-existing and inherently racy: both test methods in that class share the same topic and subscription, and by design nothing acknowledges the messages. The first method's unacked message can be redelivered into the second method's counting window, producing a 4th delivery where `expectedMessageCount(3)` demands exactly 3. The failed assertion then skips `producer.close()`, so the automatic rerun hits `ProducerBusyException` on the fixed producer name `camel-producer-1`. Happy to file a separate JIRA (and a follow-up PR) for that flaky test. In the meantime, could a committer re-run the failed job? _Claude Code on behalf of Anvith SG_ -- 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]
