You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "etzel-mes (via GitHub)" <gi...@apache.org> on 2026/10/18 10:28:19 UTC
[PR] CAMEL-25713: camel-milo - give each client connection its own executor [camel]
etzel-mes opened a new pull request, #28049:
URL: https://github.com/apache/camel/pull/28049
# Description
[CAMEL-25713](https://issues.apache.org/jira/browse/CAMEL-25713).
A `milo-client` or `milo-browse` connection handled the outcome of its write, method call, read and browse requests, and ran its reconnect job, on `Stack.sharedScheduledExecutor()`, the scheduled executor that Milo shares between all its clients. When a request fails, `SubscriptionManager.handleConnectionFailure` holds the lock of the connection and calls `OpcUaClient.disconnect()`. A CloseSession that is sent after the client noticed the lost connection waits until a reconnect attempt restores the channel or fails, and Milo schedules those attempts on that same executor. That executor has as many threads as the JVM has processors, so with one processor its only thread waits for a task that only it could run. `disconnect()` waits without a timeout, and the CloseSession starts its request timeout only once it has a channel, so nothing ends the wait: the connection is not rebuilt, its consumers stay silent after the server can be reached again, and every call that needs the lock of
the connection waits.
OPC UA clients often run on small gateways or in containers and pods, and a CPU limit of one or less gives the JVM one processor. For the issue, against Microsoft opc-plc 2.15.4 with the client limited to one CPU, a producer writing every 2 s and the traffic to the server dropped for 30 s, main (a16cccbde62) did not rebuild the connection within 60 s in 3 of 11 runs, each time with `milo-shared-scheduled-executor-0` waiting in `OpcUaClient.disconnect()`.
The change:
- Each `MiloClientConnection` now has a scheduled thread pool of its own, created by the `ExecutorServiceManager` of the `CamelContext` and shut down when the connection is closed. `MiloClientEndpoint` and `MiloBrowseEndpoint` give the connection their `CamelContext`. Milo still schedules its reconnect attempts on its shared scheduled executor, which a disconnect no longer blocks.
- Without virtual threads, the pool has as many threads as Milo's shared scheduled executor, one per processor: like that executor, it starts a thread for each task until it has them all. They end when the connection is closed. The pool belongs to the connection, so that an outage of one server, whose disconnect and connect attempts each hold a thread, does not delay the requests and reconnects of the other connections, nor the keep-alive and reconnect timers that Milo runs on its shared scheduled executor.
- Its queue is not bounded, like the queue of Milo's executor, because a rejected reconnect would end the reconnects of the connection. The rejected policy is `Abort`: a request that completes after the connection is closed fails with a `RejectedExecutionException`. With the default `CallerRuns`, a pool that is shut down drops the task, and the request would never complete.
- `close()` takes the lock that `init()` runs under, and shuts the pool down even if disposing the connection fails.
- `SubscriptionManager` is unchanged apart from one sentence of a Javadoc that said the two executors were the same.
- The upgrade guide describes the new threads.
- New `MiloClientExecutorTest`: an awaited write completes while every thread of Milo's shared scheduled executor is busy, and the threads of the pool end when the last route that uses the connection stops. Without the change both tests fail: the write times out, and no thread of the pool exists. The first test shows that the outcome of a request no longer needs a thread of Milo's executor; it does not lose the connection.
With one processor, or with virtual threads enabled (the `ExecutorServiceManager` then builds a scheduled pool with one worker), the pool has a single thread. A route that runs on it, after an awaited request or for the status of a monitored item that a reconnect could not create, must then not wait for another request of the same connection, for example through a `ProducerTemplate`. With one processor, Milo's shared scheduled executor had the same limit.
Calling `disconnectAsync()` in `handleConnectionFailure` would avoid this one wait, but the reconnect job blocks in `connect()` until the server answers or the connect times out, and on Milo's shared scheduled executor that delays the timers of every Milo client in the JVM.
The issue mentions that handling the failures on another executor could need a guard against a stale failure starting a second reconnect. The pool never has more threads than Milo's shared scheduled executor, so it adds no such race: with one thread, failures that complete during the disconnect run before the queued reconnect and find it already scheduled; with more threads, the race is the one that main has. A guard needs the failing connection in the four producer blocks that #27956 changes, so it fits better after that PR. CAMEL-25692 proposes an executor owned by the component for the subscription recovery that #27910 added; this pool could serve as that executor.
Against the same server, main (e5ae19c3361) and this change ran side by side, each with a consumer and an awaited producer on one connection, and each with its traffic dropped for 30 s. With half a CPU per client (the JVM still sees one processor), main did not rebuild the connection within 60 s in 4 of 12 runs, each time with `milo-shared-scheduled-executor-0` waiting in `OpcUaClient.disconnect()` from `handleConnectionFailure` of a write; with the change, the connection was rebuilt in all 12. With one CPU per client, both rebuilt it in all 18 runs: the hang is a race, and there the CloseSession of main always failed at once. In 6 of the 30 runs the CloseSession of the change waited about 6 s, until a reconnect attempt of the channel failed while the traffic was still dropped; on main that wait does not end.
This PR does not change the lines that #27956 (CAMEL-25694, @gnodet) and #28045 (CAMEL-25690) change. It merges with each of them without conflicts in either order, and all three merge together; on top of #27956, the new test and the tests of #27956 pass.
`mvn -Psourcecheck clean verify` in `components/camel-milo` passes (81 tests, 1 skipped as on main), and the module build regenerates no files. The module tests passed three more times with `-Dsurefire.rerunFailingTestsCount=0`, once with `-XX:ActiveProcessorCount=1`.
@davsclaus @oscerd could you take a look?
# Target
- [x] I checked that the commit is targeting the correct branch (Camel 4 uses the `main` branch)
# Tracking
- [x] 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).
# Apache Camel coding standards and style
- [x] I checked that each commit in the pull request has a meaningful subject line and body.
- [ ] I have run `mvn clean install -DskipTests` locally from root folder and I have committed all auto-generated changes.
# AI-assisted contributions
- [x] 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.
_Claude Code on behalf of etzel-mes_
--
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-25713: camel-milo - give each client connection its own executor [camel]
Posted by "davsclaus (via GitHub)" <gi...@apache.org>.
davsclaus merged PR #28049:
URL: https://github.com/apache/camel/pull/28049
--
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-25713: camel-milo - give each client connection its own executor [camel]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #28049:
URL: https://github.com/apache/camel/pull/28049#issuecomment-6250966453
:star2: Thank you for your contribution to the Apache Camel project! :star2:
:robot: CI automation will test this PR automatically.
:camel: Apache Camel Committers, please review the following items:
* First-time contributors **require MANUAL approval** for the GitHub Actions to run
* You can use the command `/component-test (camel-)component-name1 (camel-)component-name2..` to request a test from the test bot although they are normally detected and executed by CI.
* You can label PRs using `skip-tests` and `test-dependents` to fine-tune the checks executed by this PR.
* Build and test logs are available in the summary page. **Only** [Apache Camel committers](https://camel.apache.org/community/team/#committers) have access to the summary.
:warning: Be careful when sharing logs. Review their contents before sharing them publicly.
--
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-25713: camel-milo - give each client connection its own executor [camel]
Posted by "davsclaus (via GitHub)" <gi...@apache.org>.
davsclaus commented on code in PR #28049:
URL: https://github.com/apache/camel/pull/28049#discussion_r4307398068
##########
components/camel-milo/src/main/java/org/apache/camel/component/milo/client/MiloClientConnection.java:
##########
@@ -81,14 +98,40 @@ public OpcUaClient getOpcUaClient() {
}
protected void init() {
- this.manager = new SubscriptionManager(this.configuration, Stack.sharedScheduledExecutor(), 10_000);
+ ObjectHelper.notNull(this.camelContext, "camelContext");
+
+ // A failed request disconnects the client, which can wait for a reconnect attempt that Milo schedules on its shared
+ // scheduled executor, so this connection handles its requests and reconnects on an executor of its own.
+ final ThreadPoolProfile profile = new ThreadPoolProfile("MiloClient");
+ // as many threads as that executor; with one processor or with virtual threads this is one thread, so a route
+ // that continues on it after an awaited request must not wait for another request of this connection
+ profile.setPoolSize(Runtime.getRuntime().availableProcessors());
Review Comment:
Not blocking: this gives each connection a pool as large as Milo's JVM-wide one. The threads of a `ScheduledThreadPoolExecutor` never time out when idle, because Camel's scheduled pool factory ignores `keepAliveTime` and `allowCoreThreadTimeOut`. Each submitted task also starts a new thread until the pool reaches its core size. So a gateway with 8 processors and 30 PLC connections ends up with 240 idle `MiloClient` threads, where main had 8 in total. With virtual threads it is the other way round: one worker per connection, so after awaited requests the rest of every route on that connection runs on that single thread, one at a time.
The upgrade guide already describes this, so it is fine for this PR. If it turns out to matter, a follow-up could split the two jobs: a small scheduled pool for the reconnect job, and a cached pool for the request completions (one thread per task with virtual threads). Idle threads of a cached pool time out, as they do in Milo's own client executor.
--
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-25713: camel-milo - give each client connection its own executor [camel]
Posted by "davsclaus (via GitHub)" <gi...@apache.org>.
davsclaus closed pull request #28049: CAMEL-25713: camel-milo - give each client connection its own executor
URL: https://github.com/apache/camel/pull/28049
--
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-25713: camel-milo - give each client connection its own executor [camel]
Posted by "etzel-mes (via GitHub)" <gi...@apache.org>.
etzel-mes commented on code in PR #28049:
URL: https://github.com/apache/camel/pull/28049#discussion_r4310891427
##########
components/camel-milo/src/main/java/org/apache/camel/component/milo/client/MiloClientConnection.java:
##########
@@ -81,14 +98,40 @@ public OpcUaClient getOpcUaClient() {
}
protected void init() {
- this.manager = new SubscriptionManager(this.configuration, Stack.sharedScheduledExecutor(), 10_000);
+ ObjectHelper.notNull(this.camelContext, "camelContext");
+
+ // A failed request disconnects the client, which can wait for a reconnect attempt that Milo schedules on its shared
+ // scheduled executor, so this connection handles its requests and reconnects on an executor of its own.
+ final ThreadPoolProfile profile = new ThreadPoolProfile("MiloClient");
+ // as many threads as that executor; with one processor or with virtual threads this is one thread, so a route
+ // that continues on it after an awaited request must not wait for another request of this connection
+ profile.setPoolSize(Runtime.getRuntime().availableProcessors());
Review Comment:
Thanks, I measured it on a JVM limited to 8 processors (`-XX:ActiveProcessorCount=8`) against a local Milo server, two runs each:
- Idle after 30 connections: 240 `MiloClient` threads, as you wrote (319 platform threads in total, 56 on main). Resident memory did not change measurably; reserved thread stacks did.
- 30 connections × 4 callers, each awaited write followed by 10 ms of blocking work in the route: 7,200–9,500 exchanges/s, ~690/s on main, where Milo's 8 shared threads ran the routes of all connections.
- With `camel.threads.virtual.enabled=true`, 1 connection × 32 callers with the same work: ~86/s, ~670/s on main. This is the single worker you describe.
So I'll follow your suggestion in a follow-up: one scheduled thread per connection for the reconnect job and a cached pool for the request completions, so that idle threads time out and virtual threads get a thread per completion. I'll open a JIRA for it and send the PR once it is measured the same way.
_Claude Code on behalf of etzel-mes_
--
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-25713: camel-milo - give each client connection its own executor [camel]
Posted by "gnodet-bot (via GitHub)" <gi...@apache.org>.
gnodet-bot commented on code in PR #28049:
URL: https://github.com/apache/camel/pull/28049#discussion_r4306758215
##########
components/camel-milo/src/main/java/org/apache/camel/component/milo/client/MiloClientConnection.java:
##########
@@ -81,14 +98,37 @@ public OpcUaClient getOpcUaClient() {
}
protected void init() {
- this.manager = new SubscriptionManager(this.configuration, Stack.sharedScheduledExecutor(), 10_000);
+ ObjectHelper.notNull(this.camelContext, "camelContext");
+
+ // A failed request disconnects the client, which can wait for a reconnect attempt that Milo schedules on its shared
+ // scheduled executor, so this connection handles its requests and reconnects on an executor of its own.
+ final ThreadPoolProfile profile = new ThreadPoolProfile("MiloClient");
+ // as many threads as that executor; with one processor or with virtual threads this is one thread, so a route
+ // that continues on it after an awaited request must not wait for another request of this connection
+ profile.setPoolSize(Runtime.getRuntime().availableProcessors());
+ // not bounded, like that executor, because a rejected reconnect would end the reconnects of this connection
+ profile.setMaxQueueSize(-1);
+ // a request that completes after the connection is closed fails instead of being dropped
+ profile.setRejectedPolicy(ThreadPoolRejectedPolicy.Abort);
+ this.executor = this.camelContext.getExecutorServiceManager().newScheduledThreadPool(this, "MiloClient", profile);
+
+ this.manager = new SubscriptionManager(this.configuration, this.executor, 10_000);
}
@Override
public void close() throws Exception {
- if (this.manager != null) {
- this.manager.dispose();
- this.manager = null;
+ lock.lock();
+ try {
+ if (this.manager != null) {
+ this.manager.dispose();
+ this.manager = null;
+ }
+ } finally {
+ if (this.executor != null) {
+ this.camelContext.getExecutorServiceManager().shutdown(this.executor);
+ this.executor = null;
+ }
+ lock.unlock();
Review Comment:
⚠️ **Potential lock leak:** `lock.unlock()` is positioned after `camelContext.getExecutorServiceManager().shutdown(this.executor)` inside the `finally` block. If `shutdown()` throws a `RuntimeException`, `lock.unlock()` would never be called, leaving the lock permanently held.
Consider restructuring to guarantee unlock regardless of executor shutdown outcome:
```suggestion
@Override
public void close() throws Exception {
lock.lock();
try {
if (this.manager != null) {
this.manager.dispose();
this.manager = null;
}
if (this.executor != null) {
this.camelContext.getExecutorServiceManager().shutdown(this.executor);
this.executor = null;
}
} finally {
lock.unlock();
}
}
```
--
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-25713: camel-milo - give each client connection its own executor [camel]
Posted by "davsclaus (via GitHub)" <gi...@apache.org>.
davsclaus commented on PR #28049:
URL: https://github.com/apache/camel/pull/28049#issuecomment-6261564525
Closing and reopening to re-run CI against main: the `CatalogSamplesTest.callingAServiceIsTheHttpComponentNotEnrich` failure in camel-jbang-core came from main and is fixed there (bbd6f750aa00). Nothing to change in this PR.
_Claude Code on behalf of Claus Ibsen_
--
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-25713: camel-milo - give each client connection its own executor [camel]
Posted by "davsclaus (via GitHub)" <gi...@apache.org>.
davsclaus closed pull request #28049: CAMEL-25713: camel-milo - give each client connection its own executor
URL: https://github.com/apache/camel/pull/28049
--
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-25713: camel-milo - give each client connection its own executor [camel]
Posted by "etzel-mes (via GitHub)" <gi...@apache.org>.
etzel-mes commented on code in PR #28049:
URL: https://github.com/apache/camel/pull/28049#discussion_r4306832800
##########
components/camel-milo/src/main/java/org/apache/camel/component/milo/client/MiloClientConnection.java:
##########
@@ -81,14 +98,37 @@ public OpcUaClient getOpcUaClient() {
}
protected void init() {
- this.manager = new SubscriptionManager(this.configuration, Stack.sharedScheduledExecutor(), 10_000);
+ ObjectHelper.notNull(this.camelContext, "camelContext");
+
+ // A failed request disconnects the client, which can wait for a reconnect attempt that Milo schedules on its shared
+ // scheduled executor, so this connection handles its requests and reconnects on an executor of its own.
+ final ThreadPoolProfile profile = new ThreadPoolProfile("MiloClient");
+ // as many threads as that executor; with one processor or with virtual threads this is one thread, so a route
+ // that continues on it after an awaited request must not wait for another request of this connection
+ profile.setPoolSize(Runtime.getRuntime().availableProcessors());
+ // not bounded, like that executor, because a rejected reconnect would end the reconnects of this connection
+ profile.setMaxQueueSize(-1);
+ // a request that completes after the connection is closed fails instead of being dropped
+ profile.setRejectedPolicy(ThreadPoolRejectedPolicy.Abort);
+ this.executor = this.camelContext.getExecutorServiceManager().newScheduledThreadPool(this, "MiloClient", profile);
+
+ this.manager = new SubscriptionManager(this.configuration, this.executor, 10_000);
}
@Override
public void close() throws Exception {
- if (this.manager != null) {
- this.manager.dispose();
- this.manager = null;
+ lock.lock();
+ try {
+ if (this.manager != null) {
+ this.manager.dispose();
+ this.manager = null;
+ }
+ } finally {
+ if (this.executor != null) {
+ this.camelContext.getExecutorServiceManager().shutdown(this.executor);
+ this.executor = null;
+ }
+ lock.unlock();
Review Comment:
Thanks, agreed: `unlock()` now has a `finally` block of its own (928fac49f4e). I kept the shutdown of the pool in a `finally` around `dispose()` rather than after it, so that the pool is still shut down when disposing the connection fails: `Connected.dispose()` only catches the `UaException` of `disconnect()`, and `MiloClientCachingConnectionManager` removes the connection from its cache even when `close()` fails, so the threads of the pool would otherwise run until the `CamelContext` stops.
_Claude Code on behalf of etzel-mes_
--
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-25713: camel-milo - give each client connection its own executor [camel]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #28049:
URL: https://github.com/apache/camel/pull/28049#issuecomment-6251205801
<!-- ci-tested-modules -->
:test_tube: **CI tested the following changed modules:**
- `components/camel-milo`
- `docs`
---
<details><summary>:microscope: Scalpel shadow comparison — Scalpel: 8 of 706 tested, 26 compile-only — current: 8 all tested</summary>
[Maveniverse Scalpel](https://github.com/maveniverse/scalpel) detected **8 affected modules** (current approach: 8).
**Skip-tests mode would test 8 modules** (2 direct + 7 downstream), **skip tests for 26** (generated code, meta-modules)
<details><summary>Modules Scalpel would test (8)</summary>
- `camel-jbang-mcp` ← downstream of org.apache.camel:camel-catalog
- `camel-jbang-plugin-mcp` ← downstream of org.apache.camel:camel-jbang-core
- `camel-jbang-plugin-tui` ← downstream of org.apache.camel:camel-catalog
- `camel-jbang-plugin-validate` ← downstream of org.apache.camel:camel-yaml-dsl-validator
- `camel-launcher-container` ← downstream of org.apache.camel:camel-launcher
- `camel-milo` ← components/camel-milo/src/main/java/org/apache/camel/component/milo/browse/MiloBrowseEndpoint.java, components/camel-milo/src/main/java/org/apache/camel/component/milo/client/MiloClientConnection.java, components/camel-milo/src/main/java/org/apache/camel/component/milo/client/MiloClientEndpoint.java, components/camel-milo/src/main/java/org/apache/camel/component/milo/client/internal/SubscriptionManager.java, components/camel-milo/src/test/java/org/apache/camel/component/milo/MiloClientExecutorTest.java
- `camel-yaml-dsl-validator` ← downstream of org.apache.camel:camel-catalog
- `camel-yaml-dsl-validator-maven-plugin` ← downstream of org.apache.camel:camel-yaml-dsl-validator
</details>
<details><summary>Modules with tests skipped (26)</summary>
- `apache-camel`
- `camel-allcomponents`
- `camel-catalog`
- `camel-catalog-console`
- `camel-catalog-maven`
- `camel-catalog-suggest`
- `camel-componentdsl`
- `camel-endpointdsl`
- `camel-endpointdsl-support`
- `camel-itest`
- `camel-jbang-core`
- `camel-jbang-it`
- `camel-jbang-main`
- `camel-jbang-plugin-edit`
- `camel-jbang-plugin-generate`
- `camel-jbang-plugin-kubernetes`
- `camel-jbang-plugin-test`
- `camel-kamelet-main`
- `camel-launcher`
- `camel-report-maven-plugin`
- `camel-route-parser`
- `camel-yaml-dsl`
- `camel-yaml-dsl-deserializers`
- `camel-yaml-dsl-maven-plugin`
- `coverage`
- `dummy-component`
</details>
> :information_source: Shadow mode — Scalpel observes but does not affect test execution. [Learn more](https://github.com/maveniverse/scalpel)
</details>
<details><summary>All tested modules (35 modules, 5m 29s total)</summary>
**Total reactor time:** 5m 29s
| Module | Duration | Status |
| --- | --- | --- |
| Camel :: Launcher | 48.6s | SUCCESS |
| Camel :: Component DSL | 41.6s | SUCCESS |
| Camel :: JBang :: MCP | 39.7s | SUCCESS |
| Camel :: JBang :: Plugin :: Validate | 27.3s | SUCCESS |
| Camel :: Catalog :: Camel Catalog | 22.3s | SUCCESS |
| Camel :: YAML DSL :: Validator | 21.2s | SUCCESS |
| Camel :: YAML DSL | 19.1s | SUCCESS |
| Camel :: Kamelet Main | 14.9s | SUCCESS |
| Camel :: Docs | 14.6s | SUCCESS |
| Camel :: JBang :: Plugin :: Testing | 12.7s | SUCCESS |
| Camel :: JBang :: Plugin :: Kubernetes | 11.8s | SUCCESS |
| Camel :: YAML DSL :: Deserializers | 8.2s | SUCCESS |
| Camel :: Catalog :: Camel Report Maven Plugin | 7.8s | SUCCESS |
| Camel :: Catalog :: Camel Route Parser | 7.3s | SUCCESS |
| Camel :: Catalog :: Suggest (deprecated) | 6.0s | SUCCESS |
| Camel :: All Components Sync point | 5.2s | SUCCESS |
| Camel :: YAML DSL :: Validator Maven Plugin | 4.3s | SUCCESS |
| Camel :: YAML DSL :: Maven Plugins | 3.4s | SUCCESS |
| Camel :: Catalog :: Maven | 2.1s | SUCCESS |
| Camel :: Coverage | 1.7s | SUCCESS |
| Camel :: JBang :: Plugin :: Edit | 1.4s | SUCCESS |
| Camel :: Assembly | 1.3s | SUCCESS |
| Camel :: JBang :: Integration tests | 1.1s | SUCCESS |
| Camel :: JBang :: Plugin :: Generate | 1.0s | SUCCESS |
| Camel :: Catalog :: Dummy Component | 1.0s | SUCCESS |
| Camel :: Catalog :: Console | 0.9s | SUCCESS |
| Camel :: Launcher :: Container | 0.8s | SUCCESS |
| Camel :: JBang :: Main | 0.7s | SUCCESS |
| Camel :: Endpoint DSL :: Support | 0.7s | SUCCESS |
| Camel :: JBang :: Plugin :: MCP | 0.5s | SUCCESS |
| Camel :: Endpoint DSL | n/a | |
| Camel :: Integration Tests | n/a | |
| Camel :: JBang :: Core | n/a | |
| Camel :: JBang :: Plugin :: TUI | n/a | |
| Camel :: Milo | n/a | |
**Top 20 slowest modules:**
- `Camel :: Launcher` (48.6s)
- `Camel :: Component DSL` (41.6s)
- `Camel :: JBang :: MCP` (39.7s)
- `Camel :: JBang :: Plugin :: Validate` (27.3s)
- `Camel :: Catalog :: Camel Catalog` (22.3s)
- `Camel :: YAML DSL :: Validator` (21.2s)
- `Camel :: YAML DSL` (19.1s)
- `Camel :: Kamelet Main` (14.9s)
- `Camel :: Docs` (14.6s)
- `Camel :: JBang :: Plugin :: Testing` (12.7s)
- `Camel :: JBang :: Plugin :: Kubernetes` (11.8s)
- `Camel :: YAML DSL :: Deserializers` (8.2s)
- `Camel :: Catalog :: Camel Report Maven Plugin` (7.8s)
- `Camel :: Catalog :: Camel Route Parser` (7.3s)
- `Camel :: Catalog :: Suggest (deprecated)` (6.0s)
- `Camel :: All Components Sync point` (5.2s)
- `Camel :: YAML DSL :: Validator Maven Plugin` (4.3s)
- `Camel :: YAML DSL :: Maven Plugins` (3.4s)
- `Camel :: Catalog :: Maven` (2.1s)
- `Camel :: Coverage` (1.7s)
</details>
---
:gear: [View full build and test results](https://github.com/apache/camel/actions/runs/39123214694)
--
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