You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "apupier (via GitHub)" <gi...@apache.org> on 2026/10/12 12:20:55 UTC
[PR] CAMEL-25579: fix flaky HttpOAuth2TokenCachingTest under parallel builds [camel]
apupier opened a new pull request, #27724:
URL: https://github.com/apache/camel/pull/27724
When the OAuth2 token server is closed mid-test, the HTTP client may throw either HttpHostConnectException (connection refused — port already released by the OS) or NoHttpResponseException (TCP handshake completed but server closed the socket before sending a response, typically while the port is still in TIME_WAIT).
Both exceptions signal the same condition: the token endpoint is unreachable. The race is purely a TCP timing effect that becomes visible under -T1C parallel builds where OS scheduler jitter is higher.
Loosen assertExceptionExchange() in HttpOAuth2TokenCachingTest and the equivalent inline assertion in HttpOAuth2CachedTokensKeyTest to accept either exception type instead of requiring HttpHostConnectException exactly.
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] CAMEL-25579: fix flaky HttpOAuth2TokenCachingTest under parallel builds [camel]
Posted by "davsclaus (via GitHub)" <gi...@apache.org>.
davsclaus merged PR #27724:
URL: https://github.com/apache/camel/pull/27724
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] CAMEL-25579: fix flaky HttpOAuth2TokenCachingTest under parallel builds [camel]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #27724:
URL: https://github.com/apache/camel/pull/27724#issuecomment-6125239969
<!-- ci-tested-modules -->
:test_tube: **CI tested the following changed modules:**
- `components/camel-http`
> :information_source: Dependent modules were not tested because the total number of affected modules exceeded the threshold (50). Use the `test-dependents` label to force testing all dependents.
---
<details><summary>:microscope: Scalpel shadow comparison — Scalpel: 2 of 704 tested, 0 compile-only — current: 75 all tested</summary>
[Maveniverse Scalpel](https://github.com/maveniverse/scalpel) detected **2 affected modules** (current approach: 75).
**Skip-tests mode would test 2 modules** (1 direct + 1 downstream), **skip tests for 0** (generated code, meta-modules)
<details><summary>Modules only in current approach (73)</summary>
- `camel-a2a`
- `camel-ai-observability`
- `camel-as2`
- `camel-clickup`
- `camel-consul`
- `camel-cxf-rest`
- `camel-cxf-soap`
- `camel-cxf-spring-rest`
- `camel-cxf-spring-soap`
- `camel-cxf-spring-transport`
- `camel-cxf-transport`
- `camel-java-joor-dsl`
- `camel-jbang-mcp`
- `camel-jbang-plugin-mcp`
- `camel-jbang-plugin-route-parser`
- `camel-jbang-plugin-tui`
- `camel-jbang-plugin-validate`
- `camel-jetty`
- `camel-jsonpath`
- `camel-kamelet`
- `camel-knative-http`
- `camel-kubernetes`
- `camel-langchain4j-agent`
- `camel-langchain4j-chat`
- `camel-langchain4j-embeddings`
- `camel-langchain4j-embeddingstore`
- `camel-launcher-container`
- `camel-lra`
- `camel-mcp-server`
- `camel-micrometer-observability`
- `camel-micrometer-prometheus`
- `camel-netty-http`
- `camel-oauth`
- `camel-observability-services`
- `camel-odata`
- `camel-openai`
- `camel-openapi-validator`
- `camel-opentelemetry`
- `camel-opentelemetry2`
- `camel-platform-http`
- `camel-platform-http-jolokia`
- `camel-platform-http-main`
- `camel-platform-http-vertx`
- `camel-quickfix`
- `camel-rest-openapi`
- `camel-rest-postman`
- `camel-restdsl-openapi-plugin`
- `camel-sap-netweaver`
- `camel-semantic`
- `camel-slack`
- `camel-soap`
- `camel-spring-ai-chat`
- `camel-spring-rabbitmq`
- `camel-state-store`
- `camel-telegram`
- `camel-telemetry`
- `camel-telemetry-dev`
- `camel-test-main-junit5`
- `camel-test-main-junit6`
- `camel-typesafe-ai`
- `camel-undertow`
- `camel-undertow-spring-security`
- `camel-vertx-http`
- `camel-webhook`
- `camel-whatsapp`
- `camel-wolf-defender`
- `camel-xml-io-dsl`
- `camel-xml-jaxb-dsl`
- `camel-xml-jaxb-dsl-test-definition`
- `camel-xml-jaxb-dsl-test-spring`
- `camel-yaml-dsl-validator`
- `camel-yaml-dsl-validator-maven-plugin`
- `camel-zookeeper`
</details>
<details><summary>Modules Scalpel would test (2)</summary>
- `camel-graphql` ← downstream of org.apache.camel:camel-http
- `camel-http` ← components/camel-http/src/test/java/org/apache/camel/component/http/HttpOAuth2CachedTokensKeyTest.java, components/camel-http/src/test/java/org/apache/camel/component/http/HttpOAuth2TokenCachingTest.java
</details>
> :information_source: Shadow mode — Scalpel observes but does not affect test execution. [Learn more](https://github.com/maveniverse/scalpel)
</details>
---
:gear: [View full build and test results](https://github.com/apache/camel/actions/runs/38248473868)
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org