Qlik Talend Data Integration: cREST component does not return a body after Route has been migrated to patch R2025-02

Ryan_Pooya — Wed, 02 Jul 2025 05:42:15 GMT

When using a route that has been migrated from an earlier version of Talend 8 to a newer patch (R2025-02 or a later version), it is possible that certain routes may not migrate correctly. If a cREST component exists within the route and incorporates camel configuration flags within one or multiple cConfig components, the Job may encounter difficulties in successfully passing the header after building and running in the newer Studio. In the log of the route/service, subsequent to the headers being passed, the termination of the route/service (upon failure) may resemble the following:

BodyType: null
Body: [Body is null]

Cause

Starting with the R2025-02 Monthly Patch, Qlik move to Camel 4 for Routes/Services may result in existing flags being set differently within the code. Furthermore, certain flags that were compatible with Camel 2 may no longer function in Camel 4 or may have undergone changes.

Resolution

If the flags "camelContext.setStreamCaching(true)", "jakarta.ws.rs.core.Response", and/or any Camel-specific flags were incorporated into the route/service prior to its migration to patch R2025-02 (or a later version), kindly remove or modify these flags from the route.

Environment

8.0.1

article Qlik Talend Data Integration: cREST component does not return a body after Route has been migrated to patch R2025-02 in Official Support Articles

Qlik Talend Data Integration: cREST component does not return a body after Route has been migrated to patch R2025-02

Cause

Resolution

Environment