live wire
AI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat DeveloperAI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat DeveloperCLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat ErrataPLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat ErrataSECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat ErrataAI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data HubAI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat DeveloperSECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat ErrataAI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat DeveloperAI · Red Hat maps silent tool-call failures across agentic pipelinesRed HatAPI · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrantAI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM ResearchJAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errataAI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLMAI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat DeveloperAI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat DeveloperCLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat ErrataPLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat ErrataSECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat ErrataAI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data HubAI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat DeveloperSECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat ErrataAI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat DeveloperAI · Red Hat maps silent tool-call failures across agentic pipelinesRed HatAPI · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrantAI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM ResearchJAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errataAI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLM
upstreambeat.ai
releaseINTEGRATION

Camel Quarkus 3.39 turns integration routes into MCP tools

The release adds native-friendly bridges for agent tools, embedding stores and declarative RAG ingestion while staying on Java 17 and 21.

Camel route turned into MCP tool with RAG ingestion path.
AI-generated diagram
By The News Desk· Sep 3, 2026the quick take — two AI hosts, this story only

Apache Camel Quarkus 3.39.0 gives Java integration teams a more direct path from an existing Camel route to an agent-facing tool. The official release notes list a new MCP server extension that can expose ai-tool routes through Quarkus MCP Server, alongside bridges for LangChain4j agents, named embedding stores and retrieval augmentation.

The release was published Aug. 24 and supports Java 17 and 21. It aligns Camel Quarkus with the Camel 4.22 line and the Quarkus 3.39 generation while preserving the project’s native-compilation focus.

What changed

The most consequential additions sit around retrieval-augmented generation and tool execution. A new langchain4j-ingest extension provides declarative document ingestion into an embedding store. Camel Quarkus can also discover named LangChain4j embedding-store beans, automatically bridge Camel ingestion into a registered AI service’s retrieval augmentor and apply a retrieval filter hook, according to the resolved-issue list.

For tool calling, the release adds support for Camel’s ai-tool concept and an MCP server integration that exposes those routes as MCP tools. The same issue list records a scoping fix after CamelAiToolProvider attached every registered tool to Camel LangChain4j agent endpoints, a useful reminder that tool discovery is also an authorization boundary.

The release also adds native support for Camel’s Micrometer observability component, hardens Jolokia defaults, exposes application properties in the Quarkus developer console and updates the IBM MQ Jakarta client to the 10.x line. The GitHub changelog also documents native-build fixes for AWS integrations and additional OpenTelemetry test coverage.

Who should care

Teams already using Camel Quarkus for APIs, messaging or event flows can now present selected integration capabilities to MCP clients without creating a separate tool-service layer. Teams building RAG applications get a more declarative ingestion path and tighter integration between Camel routes, embedding stores and Quarkus LangChain4j services.

That convenience does not remove the need to review which routes become callable. An MCP tool can trigger the same downstream systems and credentials as the route behind it.

What to do

Before upgrading, confirm that applications run on Java 17 or 21 and test native builds against the changed extensions. For MCP deployments, enumerate the routes intended for tool exposure, verify authentication and input validation at the boundary, and check that unrelated ai-tool routes are not discoverable. RAG users should test embedding-store selection and retrieval filters with production-like documents before moving ingestion into the new declarative path.

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.