apupier opened a new pull request, #27882: URL: https://github.com/apache/camel/pull/27882
JmsRequestReplyExclusiveReplyToTest and JmsRequestReplyExclusiveReplyToComponentTest assert that 5 request/reply calls over an exclusive replyTo queue complete in less than 4200 ms. This check dates from CAMEL-4202, which introduced replyToType=Exclusive: an exclusive reply queue needs no JMS message selector and caches its consumer, so it is expected to be much faster than a shared one (JmsRequestReplySharedReplyToTest asserts the opposite, > 2 s). Run alone the 5 calls take about 90 ms, so the threshold is a loose ceiling that must be kept. The failures reported in CAMEL-25664 (11928 ms, 8629 ms, and a 20 s latch timeout in JmsRequestReplyExclusiveReplyToConcurrentTest) come from CPU/broker contention: camel-jms enables JUnit parallel class execution (camel.surefire.parallel=true), and these classes ran in the shared pool next to many other tests using the in-VM Artemis broker (the concurrent test was in the not-parallel group, which still runs with forkCount=4). Tag the three classes with "exclusive" so that they run in the dedicated exclusive-test surefire execution (forkCount=2, reuseForks=false), which the default-test and serials-test executions exclude. The timing assertions are unchanged. Co-authored-by: IBM Bob 2.2.1 # Description <!-- - Write a pull request description that is detailed enough to understand what the pull request does, how, and why. --> # Target - [ ] I checked that the commit is targeting the correct branch (Camel 4 uses the `main` branch) # Tracking - [ ] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). <!-- # *Note*: trivial changes like, typos, minor documentation fixes and other small items do not require a JIRA issue. In this case your pull request should address just this issue, without pulling in other changes. --> # Apache Camel coding standards and style - [ ] I checked that each commit in the pull request has a meaningful subject line and body. <!-- If you're unsure, you can format the pull request title like `[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the appropriate JIRA issue. --> - [ ] I have run `mvn clean install -DskipTests` locally from root folder and I have committed all auto-generated changes. <!-- You can run the aforementioned command in your module so that the build auto-formats your code. This will also be verified as part of the checks and your PR may be rejected if if there are uncommited changes after running `mvn clean install -DskipTests`. You can learn more about the contribution guidelines at https://github.com/apache/camel/blob/main/CONTRIBUTING.md --> # AI-assisted contributions - [ ] If this PR includes AI-generated code, commits have proper co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR description identifies the AI tool used. -- 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]
