Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Release Notes for Red Hat build of Apache Camel for Quarkus
Release Notes for Red Hat build of Apache Camel for Quarkus
Abstract
Preface
Providing feedback on Red Hat build of Apache Camel documentation
To report an error or to improve our documentation, log in to your Red Hat Jira account and submit an issue. If you do not have a Red Hat Jira account, then you will be prompted to create an account.
Procedure
- Click the following link to create ticket
- Enter a brief description of the issue in the Summary.
- Provide a detailed description of the issue or enhancement in the Description. Include a URL to where the issue occurs in the documentation.
- Clicking Submit creates and routes the issue to the appropriate documentation team.
Chapter 1. Release notes for Red Hat build of Apache Camel for Quarkus 3.15 / 3.15.3.SP2
1.1. Red Hat build of Apache Camel for Quarkus features
- Fast startup and low RSS memory
- Using the optimized build-time and ahead-of-time (AOT) compilation features of Quarkus, your Camel application can be pre-configured at build time resulting in fast startup times.
- Application generator
- Use the Quarkus application generator to bootstrap your application and discover its extension ecosystem.
- Highly configurable
All the important aspects of a Red Hat build of Apache Camel for Quarkus application can be set up programmatically with CDI (Contexts and Dependency Injection) or by using configuration properties. By default, a CamelContext is configured and automatically started for you.
Check out the Configuring your Quarkus applications by using a properties file guide for more information on the different ways to bootstrap and configure an application.
- Integrates with existing Quarkus extensions
- Red Hat build of Apache Camel for Quarkus provides extensions for libraries and frameworks that are used by some Camel components which inherit native support and configuration options.
1.2. Supported platforms, configurations, databases, and extensions
For information about supported platforms, configurations, and databases in Red Hat build of Apache Camel for Quarkus version 3.15, see the Supported Configuration page on the Customer Portal (login required).
For a list of Red Hat Red Hat build of Apache Camel for Quarkus extensions and the Red Hat support level for each extension, see the Extensions Overview chapter of the Red Hat build of Apache Camel for Quarkus Reference (login required).
1.3. BOM files for Red Hat build of Apache Camel for Quarkus
-
To configure your Red Hat Red Hat build of Apache Camel for Quarkus version 3.15 projects to use the supported extensions, use the latest Bill Of Materials (BOM) version
3.15.3.SP2-redhat-00001or newer, from the Redhat Maven Repository.
For more information about BOM dependency management, see Developing Applications with Red Hat build of Apache Camel for Quarkus
1.4. Technology preview extensions
Items designated as Technology Preview in the Extensions Overview chapter of the Red Hat build of Apache Camel for Quarkus Reference have limited supportability, as defined by the Technology Preview Features Support Scope.
1.5. Product errata and security advisories
1.5.1. Red Hat build of Apache Camel for Quarkus
For the latest Red Hat build of Apache Camel for Quarkus product errata and security advisories, see the Red Hat Product Errata page.
1.5.2. Red Hat build of Quarkus
For the latest Red Hat build of Quarkus product errata and security advisories, see the Red Hat Product Errata page.
1.6. Known issues
1.6.1. Websocket + Knative does not work with HTTP2
We support both camel-quarkus-grpc and camel-vertx-websocket with Knative.
gRPC needs HTTP2 (you can find instructions on how to enable it here: HTTP2 on Knative).
Unfortunately, Websockets with Knative does not work with HTTP2 (see Ingress Operator in OpenShift Container Platform).
Consequently, if you have an application that is intended to accept WebSocket connections, it must not allow negotiating the HTTP/2 protocol or else clients will fail to upgrade to the WebSocket protocol.
1.7. Known Quarkus CXF issues
CXF is fully supported, but the following issues remain with this release of Red Hat build of Apache Camel for Quarkus.
1.7.1. Name clash between Service methods with the same name in one Java package
If there are two SEIs in one Java package, both having a @WebMethod with the same name but different signature, then the default name for the generated request, response and possibly other classes is the same for both methods of both classes.
Since Quarkus CXF 3.10.0 and 3.8.4, the problem is detected at build time and the build fails.
1.8. Important notes
1.8.1. Support for IBM Power and IBM Z
Red Hat build of Apache Camel for Quarkus is supported on IBM Power and IBM Z.
1.8.2. Minimum Java version - JDK 17
Red Hat build of Apache Camel for Quarkus version 3.15 requires JDK 17 or newer.
1.8.3. Support for OpenJDK
Red Hat build of Apache Camel for Quarkus version 3.15 includes support for OpenJDK 21.
1.8.4. Support for AdoptiumJDK
Red Hat build of Apache Camel for Quarkus version 3.15 includes support for AdoptiumJDK 17 and AdoptiumJDK 21.
1.9. Resolved issues
The following lists shows known issues that were affecting Red Hat build of Apache Camel for Quarkus, which have been fixed in Red Hat build of Apache Camel for Quarkus version 3.15.
| Issue | Description |
|---|---|
| CVE-2025-27636 org.apache.camel/camel-http: bypass of header filters via specially crafted response [rhboac-camel-quarkus-3] | |
| CVE-2025-27636 org.apache.camel/camel-http-base: bypass of header filters via specially crafted response [rhboac-camel-quarkus-3] |
| Issue | Description |
|---|---|
| CVE-2025-1247 io.quarkus/quarkus-rest: Quarkus REST Endpoint Request Parameter Leakage Due to Shared Instance | |
| CVE-2025-24970 io.netty/netty-handler: SslHandler doesn’t correctly validate packets which can lead to native crash when using native SSLEngine | |
| CVE-2025-1634 quarkus-resteasy: Memory Leak in Quarkus RESTEasy Classic When Client Requests Timeout |
| Issue | Description |
|---|---|
| A flaw in Quarkus-HTTP, incorrectly parses cookies with certain value-delimiting characters in incoming requests. This resolves CVE-2024-12397 com.redhat.quarkus.platform/quarkus-camel-bom: Quarkus HTTP Cookie Smuggling |
| Issue | Description |
|---|---|
|
| |
|
|
1.10. Deprecated features in Red Hat build of Apache Camel for Quarkus version 3.15
The following capabilities are not available in the next major release of Red Hat build of Apache Camel for Quarkus, and are deprecated in this release.
1.10.1. Openapi-java support for Openapi v2
Deprecated features
OpenApi V2 is deprecated in 3.15, due to dropped support in Openapi-java with Camel 4.5.x.
1.11. Extensions added in Red Hat build of Apache Camel for Quarkus version 3.15
The following table lists the extensions added in the Red Hat build of Apache Camel for Quarkus version 3.15 release .
| Extension | Artifact | Description | |
|---|---|---|---|
| 1 | AWS Secrets Manager | Manage AWS Secrets Manager services using AWS SDK version 2.x. | |
| 2 | Azure Event Hubs | Integrates Azure Event Hubs using AMQP protocol. | |
| 3 | Azure Key Vault | Manage secrets and keys in Azure Key Vault Service | |
| 4 | Azure Storage Blob | Store and retrieve blobs from Azure Storage Blob Service using SDK v12. | |
| 5 | Azure Storage Queue | Storing and retrieving the messages to/from Azure Storage Queue using Azure SDK v12. | |
| 6 | Beanio | Marshal and unmarshal Java beans to and from flat files (such as CSV, delimited, or fixed length formats). | |
| 7 | Elasticsearch Low level Rest Client | Perform queries and other operations on Elasticsearch or OpenSearch (uses low-level client). | |
| 8 | File cluster service | Provides a FileLock implementation of the Camel Cluster Service SPI. | |
| 9 | Flink | Send DataSet jobs to an Apache Flink cluster. | |
| 10 | Google Secret Manager | Manage Google Secret Manager Secrets | |
| 11 | GraphQL | Send GraphQL queries and mutations to external systems. | |
| 12 | Hashicorp Vault | Manage secrets in Hashicorp Vault Service. | |
| 13 | JQ | Evaluate JQ expression against a JSON message body. | |
| 14 | Kubernetes Cluster Service | Provides a Kubernetes implementation of the Camel Cluster Service SPI | |
| 15 | Qute | Transform messages using Quarkus Qute templating engine. | |
| 16 | RabbitMQ | Send and receive messages from RabbitMQ using Spring RabbitMQ client. | |
| 17 | SMB | SMB component which consumes natively from file shares using the Server Message Block (SMB, also known as Common Internet File System - CIFS) protocol. | |
| 18 | YAML IO | Camel XML DSL with camel-xml-io. |
1.12. Extensions removed in Red Hat build of Apache Camel for Quarkus version 3.15
No extensions are removed in the Red Hat build of Apache Camel for Quarkus version 3.15 release.
1.13. Extensions with changed support in Red Hat build of Apache Camel for Quarkus version 3.15
The following table lists the extensions that have changed support levels in the Red Hat build of Apache Camel for Quarkus version 3.15 release.
| Extension | Artifact | Description |
|---|---|---|
| Azure Storage Blob |
| Store and retrieve blobs from Azure Storage Blob Service using SDK v12. |
| Azure Storage Queue |
| Storing and retrieving the messages to/from Azure Storage Queue using Azure SDK v12. |
For information about support levels, see Red Hat build of Apache Camel for Quarkus Extensions
1.14. Data formats added in Red Hat build of Apache Camel for Quarkus version 3.15
No data formats have been added in the Red Hat build of Apache Camel for Quarkus version 3.15 release.
