Chapter 1. Red Hat build of Apache Camel for Spring Boot 4.8 release notes
1.1. Features in Red Hat build of Apache Camel for Spring Boot
Red Hat build of Apache Camel for Spring Boot introduces Camel support for Spring Boot which provides auto-configuration of Camel, and starters for many Camel components. The opinionated auto-configuration of the Camel context auto-detects Camel routes available in the Spring context and registers key Camel utilities (like producer template, consumer template and the type converter) as beans.
1.2. Supported platforms, configurations, databases, and extensions for Red Hat build of Apache Camel for Spring Boot
- For information about supported platforms, configurations, and databases in Red Hat build of Apache Camel for Spring Boot, see the Supported Configuration page on the Customer Portal (login required).
- For a list of Red Hat Red Hat build of Apache Camel for Spring Boot extensions, see the Red Hat build of Apache Camel for Spring Boot Reference (login required).
1.3. The javax to jakarta Package Namespace Change
The Java EE move to the Eclipse Foundation and the establishment of Jakarta EE, since Jakarta EE 9, packages used for all EE APIs have changed to jakarta.*
Code snippets in documentation have been updated to use the jakarta.* namespace, but you of course need to take care and review your own applications.
This change does not affect javax packages that are part of Java SE.
When migrating applications to EE 10, you need to:
-
Update any import statements or other source code uses of EE API classes from the
javaxpackage tojakarta. -
Change any EE-specified system properties or other configuration properties whose names begin with
javax.to begin withjakarta.. -
Use the
META-INF/services/jakarta.[rest_of_name]name format to identify implementation classes in your applications that use the implement EE interfaces or abstract classes bootstrapped with thejava.util.ServiceLoadermechanism.
1.3.1. Migration tools
- Source code migration: How to use Red Hat Migration Toolkit for Auto-Migration of an Application to the Jakarta EE 10 Namespace
- Bytecode transforms: For cases where source code migration is not an option, the open source Eclipse Transformer
Additional resources
- Background: Update on Jakarta EE Rights to Java Trademarks
- Red Hat Customer Portal: Red Hat JBoss EAP Application Migration from Jakarta EE 8 to EE 10
- Jakarta EE: Javax to Jakarta Namespace Ecosystem Progress
1.4. Important notes for Red Hat build of Apache Camel for Spring Boot
1.4.1. Support for IBM Power and IBM Z
Red Hat build of Camel Spring Boot is now supported on IBM Power and IBM Z.
1.4.2. Changes to the snowdrop groupId
The snowdrop groupId is changed from me.snowdrop to dev.snowdrop. You must update the pom.xml file accordingly.
1.4.3. Using the automatic Camel context reloading on Secret Refresh feature of AWS Secret Manager component starter
To use the Automatic Camel context reloading on Secret Refresh feature, the secret update has to be done either via UI or via API call with opereation PutSecretValue. The camel context reload will not be triggered with executing updateSecret via Camel.
1.5. Fixed issues for Red Hat build of Apache Camel for Spring Boot
The following sections list the issues that have been resolved in Red Hat build of Apache Camel for Spring Boot.
1.5.1. Red Hat build of Apache Camel for Spring Boot version 4.8.5 fixed issues
The following sections list the issues that have been resolved in Red Hat build of Apache Camel for Spring Boot version 4.8.5.
| Issue | Description |
|---|---|
| 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-2240 io.smallrye/smallrye-fault-tolerance-core: SmallRye Fault Tolerance | |
| CVE-2025-27636 org.apache.camel/camel-http: bypass of header filters via specially crafted response | |
| CVE-2025-27636 org.apache.camel/camel-http-base: bypass of header filters via specially crafted response | |
| CVE-2024-57699 json-smart: Potential DoS via stack exhaustion | |
| CVE-2025-22228 spring-security-core: CVE-2025-22228: Spring Security BCryptPasswordEncoder does not enforce maximum password length |
1.5.2. Red Hat build of Apache Camel for Spring Boot version 4.8.3 fixed issues
The following sections list the issues that have been resolved in Red Hat build of Apache Camel for Spring Boot version 4.8.3.
| Issue | Description |
|---|---|
| Camel JBang Export/Run are not working based on camel-version setting | |
| Platform-http doesn’t remove methods on Camel context reload | |
|
CVE-2024-53990 org.asynchttpclient/async-http-client: AsyncHttpClient (AHC) library’s | |
| camel-platform-http-starter HttpBinding does not support concurrent multipart/form-data requests with the same key id | |
| CVE-2024-12798 ch.qos.logback/logback-core: arbitrary code execution via JaninoEventEvaluator | |
| CVE-2024-52046 org.apache.mina/mina-core: Apache MINA: applications using unbounded deserialization may allow RCE | |
| Camel Opentelemetry, add the RouteID attribute to every span. | |
| GZIPOutInterceptor : ensure the CXF headers that GZIPOutInterceptor needs to resize is modifiable | |
| CXF opentelemetry - using same trace id from different http requests |
1.5.3. Red Hat build of Apache Camel for Spring Boot version 4.8.0 fixed issues
The following sections list the issues that have been resolved in Red Hat build of Apache Camel for Spring Boot version 4.8.0.
| Issue | Description |
|---|---|
| Add support for camel-opensearch | |
| Requestion BeanIO counting character length by bytes | |
| Implement the kafka consumer’s "offsetsForTimes" method on the Kafka consumer | |
| Improve logging of offliner tool | |
| Allow to configure Offsets position and Offsets timestamp as property for Camel Kafka Component | |
| support Hashicorp vault | |
| Define Agroal version in CSB platform BOM | |
| Marshaling the surrogate pair characters by camel-jackson results with Garbled characters | |
| Lack of jolokia in the base image causes hawtio-online connection error "Jolokia Connect Error - Bad Gateway (502)" | |
| Refactor and remove the cxf-rt-transports-jetty/cxf-rt-transports-netty-server/cxf-rt-transports-undertow | |
| Circular dependency error when restConfiguration is defined in a Spring beans XML | |
| OpenTelemetry missing traces, spans and or context | |
| [CAMEL-20790]kafka batching consumer polls randomly failing with NPE under load | |
| camel-rest - Code first should use actual values for property placeholders in dumped API spec | |
| CVE-2024-7254 protobuf: StackOverflow vulnerability in Protocol Buffers | |
| Create docs for kafka consumer’s "offsetsForTimes" method | |
| Excessing locking in camel jaxb under load | |
| support component camel-azure-key-vault | |
| support component camel-google-secret-manager | |
| support component camel-aws-secrets-manager | |
| CVE-2021-44549 org.eclipse.angus/angus-mail: Enabling Secure Server Identity Checks for Safer SMTPS Communication | |
| [CAMEL-21300]camel-platform-http - Consumer should have option to control if writing response failing should cause Exchange to fail | |
| Camel-rest with undertow: Occassional ConcurrentModificationException | |
| Address CXF Async Calls with OpenTelemetry | |
| Camel-CICS - CTG6662E This JavaGateway instance is already open | |
| [CAMEL-21329] camel-zipfile - Null body is not supported by ZipAggregationStrategy | |
| CVE-2024-38816 org.springframework/spring-webmvc: Path Traversal Vulnerability in Spring Applications Using RouterFunctions and FileSystemResource | |
| CVE-2024-47561 org.apache.avro/avro: Schema parsing may trigger Remote Code Execution (RCE) | |
| JsonPath cant read message body coming from platform-http by default | |
| platform-http Large File Streaming | |
| platform-http Write Response Handler Error | |
| camel-http does not support socketTimeout option anymore | |
| For camel-crypto component, it is not possible to use "inline" with "AES/GCM/NoPadding" | |
| CVE-2024-31141 org.apache.kafka/kafka-clients: privilege escalation to filesystem read-access via automatic ConfigProvider | |
| camel-opentelemetry: the camel spans are not present anymore on the traces | |
| platform-http-starter handle attachments | |
| platfrom-http-starter enforce produces and consumes configuration |
1.6. Known issues for Red Hat build of Apache Camel for Spring Boot
The following sections list known issues for Red Hat build of Apache Camel for Spring Boot.
1.6.1. Red Hat build of Apache Camel for Spring Boot version 4.8.3 known issues
- CSB-6437 CXF opentelemetry - using same trace id from different http requests on RHEL9
-
This issue only occurs with CXF and OpenTelemetry with the custom tracing configuration on RHEL 9 platform. ,In case of CXF and opentelemetry with the custom opentelemetry tracer defined, when you call multiple requests, the trace ID seems to be reused in the Camel routes. The result is that new spans are added in the existing traces for each http request, instead of creating one new trace ID for each http request. The workaround is to explicitly define the
ContextPropagatorstoW3CTraceContextPropagatoras shown in the example below:
@Bean
ContextPropagators contextPropagators() {
// return ContextPropagators.create(TextMapPropagator.composite(W3CBaggagePropagator.getInstance()));
return ContextPropagators.create(W3CTraceContextPropagator.getInstance());
}1.6.2. Red Hat build of Apache Camel for Spring Boot version 4.8.0 known issues
- CSB-4318 Fail to deploy on OCP using Openshift Maven Plugin if spring.boot.actuator.autoconfigure is not in the dependencies
Jkube maven plugin uses the following condition to check if the application exposes health endpoint (using
SpringBootHealthCheckEnricher). Both classes are in the classpath:-
org.springframework.boot.actuate.health.HealthIndicator -
org.springframework.web.context.support.GenericWebApplicationContext
-
However, the /actuator/health wil be not exposed without the configuration of the actuator. This creates discordance between the readiness/liveness probes configured by JKube (they both uses the above endpoint) and what the application is exposing.
This misconfiguration causes a failing deployment config on OpenShift Container Platform since the generated pod will never be in Ready status since the probe`s call for an endpoint is not configured. So in order to make the application work on OpenShift Container Platform, which is deployed using JKube (openshift-maven-plugin), it is necessary to have both web and actuator autoconfiguration in the dependencies.
Following example shows how to configure web and actuator autoconfiguration.
Example
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-actuator</artifactId>
</dependency>Update the archetype as shown below. The applications built from the following archetype will be deployed correctly using JKube.
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
<exclusions>
<exclusion>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-tomcat</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-undertow</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-actuator</artifactId>
</dependency>This issue affects the custom applications with missing one of the above dependencies.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}