apupier opened a new pull request, #28687: URL: https://github.com/apache/camel/pull/28687
pathParameterIsRejected sent two requests in a row to the same endpoint URL. The server closes the channel after answering a rejected request with 400, and the producer can pick that channel up again for the second request. When the close wins the race, the client fails with a CamelExchangeException (No response received from remote server) instead of a NettyHttpOperationFailedException with status 400. Send the encoded path parameter request in its own test so that it starts with a fresh producer and cannot reuse a channel being closed. Reproduction attempts (20 runs of the test class each): - original test, unchanged: 20 passed, the race is not hit locally - original test with a Thread.sleep(500) between the two requests: 20 passed, the sleep only gives the server time to close the channel - original test with a temporary 300 ms delay in the server before it closes the channel after the 400 (not committed): 20 failed with the error reported in the JIRA - fixed test with the same temporary server delay: 20 passed 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]
