Chapter 1. Release notes for Red Hat build of Apache Camel for Quarkus 3.27 / 3.27.3.SP2

For the latest Red Hat build of Apache Camel for Quarkus product errata and security advisories, see the Red Hat Product Errata page.

For the latest Red Hat build of Quarkus product errata and security advisories, see the Red Hat Product Errata page.

This affects quarkus-jdbc-postgresql.

When running a maven build with Red Hat build of Apache Camel for Quarkus version 3.27.3.SP2-redhat-00001, the build fails with with a java.lang.ref.Cleaner error, similar to this:

Error: Detected a java.lang.ref.Cleaner object in the image heap which uses a daemon thread that invokes cleaning actions, but threads running in the image generator are no longer running at image runtime.
    ...

The error is caused by a mismatch between version numbers in Quarkus core and the Postgres JDBC driver dependency.

In this release, some important limitations apply to the Groovy extension.

quarkus.native.report-errors-at-runtime=true

from("direct:start")
    .transform().groovy("println '{{greeting.message}}'");

The endChoice method is changed to end().endChoice() (see CEQ-11181).

When using Choice EIP then in some situations you may need to use .endChoice() to be able to either continue added more nodes to the current Choice EIP, or that you are working with nested Choice EIPs (choice inside choice), then you may also need to use endChoice to go back to the parent choice to continue from there.

However, there has been some regressions from upgrading older Camel releases to 4.11, and therefore we have refactored endChoice to work more consistent.

For example, the following code:

from("direct:start")
    .choice()
        .when(header("foo").isGreaterThan(1))
            .choice()
                .when(header("foo").isGreaterThan(5))
                    .to("mock:big")
                .otherwise()
                    .to("mock:med")
            .endChoice()
        .otherwise()
            .to("mock:low")
        .end();

Should now be:

from("direct:start")
    .choice()
        .when(header("foo").isGreaterThan(1))
            .choice()
                .when(header("foo").isGreaterThan(5))
                    .to("mock:big")
                .otherwise()
                    .to("mock:med")
            .end().endChoice()
        .otherwise()
            .to("mock:low")
        .end();

The change of endChoice method to end().endChoice() makes the calls consistent.

This ends the current (inner) choice and changes the scope to Choice EIP to be able to continue in the previous (outer) choice.

This informs Java DSL that the scope is Choice EIP and you can add the otherwise block to the outer choice, which would otherwise not work.

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.

When running a maven update with a specified version:

mvn com.redhat.quarkus.platform:quarkus-maven-plugin:{camel-quarkus-maven-plugin-version}:update -Drewrite

This can cause an error similar to this:

Failed to apply the updates: The project is missing the Quarkus platform BOM in module foo.

The affected modules are specific to your project, so you need to read the error message to find the affected modules.

When running a camel CLI project export, the export may fail with errors related to missing artifacts or classes.

As a workaround, before installing Camel CLI, you can add Red Hat repositories to your local Maven configuration file.

Red Hat build of Apache Camel for Quarkus is supported on IBM Power and IBM Z.

Red Hat build of Apache Camel for Quarkus version 3.27 requires JDK 17 or newer.

Red Hat build of Apache Camel for Quarkus version 3.27 includes support for OpenJDK 21.

Red Hat build of Apache Camel for Quarkus version 3.27 includes support for AdoptiumJDK 17 and AdoptiumJDK 21.

For important information about upgrading Camel, see the Apache Camel manual sections:

Red Hat build of Apache Camel for Quarkus version 3.27 has been upgraded from Camel version 4.10.4 to Camel version 4.14.2. For additional information about each intervening Camel patch release, refer to the following:

Red Hat build of Apache Camel for Quarkus version 3.27 has been upgraded from Camel Quarkus version 3.20 to Camel Quarkus version 3.27. For additional information about each intervening Camel Quarkus patch release, refer to the following:

The camel-quarkus-jolokia register-management-endpoint default has been changed to false.

When using camel-quarkus-jolokia, the /q/jolokia Quarkus management endpoint is no longer registered by default. It has been deprecated for removal in a future release.

If you need to restore the previous behavior and expose /q/jolokia, you can add the following to application.properties.

quarkus.camel.jolokia.register-management-endpoint=true

However, as mentioned above, this option will eventually be removed.

The Apache Olingo project has been retired.

The Olingo4 component camel-olingo4 is deprecated in this release.

There is currently no viable replacement component, although `camel-sap´ might work for limited cases.

This document may help when upgrading from the 3.20 LTS stream to 3.27 LTS stream.

Unable to dispatch SOAP client call within 30000 ms on a worker thread due to worker thread pool exhaustion.
You may want to adjust one or more of the following configuration options:
quarkus.thread-pool.core-threads, quarkus.thread-pool.max-threads, quarkus.cxf.client.worker-dispatch-timeout

<?xml version='1.0' encoding='UTF-8'?>
<wsdl:definitions
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://test.deployment.cxf.quarkiverse.io/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:ns1="http://schemas.xmlsoap.org/soap/http"
    name="ExtensorsService"
    targetNamespace="http://test.deployment.cxf.quarkiverse.io/"
    xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" >
...
  <wsdl:portType name="ExtensorsServiceGet" />
  <wsdl:binding name="ExtensorsServiceGet" type="tns:ExtensorsServiceGet">
    <http:binding verb="GET" />
  </wsdl:binding>
  <wsdl:service name="ExtensorsService">
    <wsdl:port binding="tns:ExtensorsServiceGet" name="ExtensorsServiceGet" >
      <http:address location="http://localhost:8081/soap/ExtensorsServiceGet" />
    </wsdl:port>
  </wsdl:service>
</wsdl:definitions>

ERROR [io.qua.run.Application] (main) Failed to start application: java.lang.RuntimeException: Failed to start quarkus
        at io.quarkus.runner.ApplicationImpl.doStart(Unknown Source)
        ...
Caused by: org.apache.cxf.service.factory.ServiceConstructionException: SERVICE_CREATION_MSG
        at org.apache.cxf.wsdl11.WSDLServiceFactory.<init>(WSDLServiceFactory.java:87)
        ...
Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:binding[2]/http:binding): faultCode=CONFIGURATION_ERROR: Problem instantiating Java extensionType 'com.ibm.wsdl.extensions.http.HTTPBindingImpl'.: java.lang.InstantiationException: com.ibm.wsdl.extensions.http.HTTPBindingImpl
        at javax.wsdl.extensions.ExtensionRegistry.createExtension(ExtensionRegistry.java:383)
        ...
Caused by: java.lang.InstantiationException: com.ibm.wsdl.extensions.http.HTTPBindingImpl
        at java.base@21.0.8/java.lang.Class.newInstance(DynamicHub.java:719)
        ...
Caused by: java.lang.NoSuchMethodException: com.ibm.wsdl.extensions.http.HTTPBindingImpl.<init>()
        at java.base@21.0.8/java.lang.Class.checkMethod(DynamicHub.java:1078)
        at java.base@21.0.8/java.lang.Class.getConstructor0(DynamicHub.java:1241)
        at java.base@21.0.8/java.lang.Class.newInstance(DynamicHub.java:706)
        ... 28 more