Chapter 1. Release notes for Red Hat build of Apache Camel for Quarkus 3.15 / 3.15.3.SP1

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.SP1-redhat-00002 or 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

Note

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.

Table 1.1. Red Hat build of Apache Camel for Quarkus resolved issues in version 3.15.3.SP1
Issue	Description
CEQ-10793	CVE-2025-1247 io.quarkus/quarkus-rest: Quarkus REST Endpoint Request Parameter Leakage Due to Shared Instance
CEQ-10790	CVE-2025-24970 io.netty/netty-handler: SslHandler doesn’t correctly validate packets which can lead to native crash when using native SSLEngine
CEQ-10850	CVE-2025-1634 quarkus-resteasy: Memory Leak in Quarkus RESTEasy Classic When Client Requests Timeout

Table 1.2. Red Hat build of Apache Camel for Quarkus resolved issues in version 3.15.3
Issue	Description
CEQ-10644	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

Table 1.3. Red Hat build of Apache Camel for Quarkus resolved issues in version 3.15.0
Issue	Description
CEQ-10425	`camel-platform-http` - Consumer should have option to control if writing response failing should cause Exchange to fail
CEQ-10383	`camel-smb` does not work if path != "/"

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 .

Table 1.4. Added extensions
	Extension	Artifact	Description
1	AWS Secrets Manager	camel-quarkus-aws-secrets-manager	Manage AWS Secrets Manager services using AWS SDK version 2.x.
2	Azure Event Hubs	camel-quarkus-azure-eventhubs	Integrates Azure Event Hubs using AMQP protocol.
3	Azure Key Vault	camel-quarkus-azure-key-vault	Manage secrets and keys in Azure Key Vault Service
4	Azure Storage Blob	camel-quarkus-azure-storage-blob	Store and retrieve blobs from Azure Storage Blob Service using SDK v12.
5	Azure Storage Queue	camel-quarkus-azure-storage-queue	Storing and retrieving the messages to/from Azure Storage Queue using Azure SDK v12.
6	Beanio	camel-quarkus-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	camel-quarkus-elasticsearch-rest-client	Perform queries and other operations on Elasticsearch or OpenSearch (uses low-level client).
8	File cluster service	camel-quarkus-file-cluster-service	Provides a FileLock implementation of the Camel Cluster Service SPI.
9	Flink	camel-quarkus-flink	Send DataSet jobs to an Apache Flink cluster.
10	Google Secret Manager	camel-quarkus-google-secret-manager	Manage Google Secret Manager Secrets
11	GraphQL	camel-quarkus-graphql	Send GraphQL queries and mutations to external systems.
12	Hashicorp Vault	camel-quarkus-hashicorp-vault	Manage secrets in Hashicorp Vault Service.
13	JQ	camel-quarkus-jq	Evaluate JQ expression against a JSON message body.
14	Kubernetes Cluster Service	camel-quarkus-kubernetes-cluster-service	Provides a Kubernetes implementation of the Camel Cluster Service SPI
15	Qute	camel-quarkus-qute	Transform messages using Quarkus Qute templating engine.
16	RabbitMQ	camel-quarkus-spring-rabbitmq	Send and receive messages from RabbitMQ using Spring RabbitMQ client.
17	SMB	camel-quarkus-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-quarkus-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	`camel-quarkus-azure-storage-blob`	Store and retrieve blobs from Azure Storage Blob Service using SDK v12.
Azure Storage Queue	`camel-quarkus-azure-storage-queue`	Storing and retrieving the messages to/from Azure Storage Queue using Azure SDK v12.