Skip to main content Skip to complementary content

Talend Remote Engine v2.13.13

Talend Remote Engine v2.13.13 is generally available.

New features

Feature Description
SSL communication The engine installer now provides an option to automatically enable Secure Sockets Layer (SSL) communication between Talend Remote Engine and its JobServer, simplifying the SSL setup process.

For further information, see the SSL setup step in Installing the Remote Engine automatically.

SSH password The engine installer can generate a strong password for SSH communication with Talend Remote Engine. You can manually update this password.

For more information, see the SSH-related step in Installing the Remote Engine automatically.

Security enhancements

Issues Description
DPE-1132 The following engine dependencies have been upgraded to address potential vulnerabilities and improve overall security:
  • Spring Framework: 6.2.5 to 6.2.8, addressing CVE-2025-41234
  • Spring Vault: 3.1.2 to 3.2.0
  • Jackson library: 2.18.3 to 2.19.1
  • Google Gson: 2.12.1 to 2.13.1
  • Google Guava: 33.4.6-jre to 33.4.8-jre
  • Apache HTTP Client 5: 5.4.3 to 5.5
  • Apache Commons Text: 1.13.0 to 1.13.1
  • Apache Commons IO: 2.18.0 to 2.19.0
  • Apache ActiveMQ client: 5.18.7 to 5.19.0
  • Apache CXF: 3.6.6 to 3.6.7
  • OSHI library: 6.8.0 to 6.8.2
  • Picocli library: 4.7.6 to 4.7.7
DPE-929 The Apache Karaf version used by Talend Remote Engine has been upgraded to 4.4.7 to enhance stability, performance, and security.

Notable fixes

Issues Description
DPE-1047 Fixed an issue where Job executions failed after a Remote Engine upgrade due to a missing GPG path (SUPPORT-3386).
DPE-1346 Upgraded org.ops4j.pax.url:pax-url-aether to version 2.6.17, resolving a Remote Engine restart issue triggered by a Java heap space OutOfMemoryError (SUPPORT-3868).
DPE-1273 Addressed a problem where CBP (capacity-based pricing) metrics were not sent. This problem triggered the restart of all microservices on Remote Engine v2.13.11 (SUPPORT-4144).

Deprecated and removed items

Feature Description
Token refresh for Box connection Native support for the Box connector was removed from Talend Management Console in the R2025-05 release. As a result, automatic token refresh for Box connections is no longer supported and removed from Talend Remote Engine.

For more information on managing connections in Talend Management Console, see Connection or Managing connections.

Known issues

Issues Description
Hanging engine CLI The Talend Remote Engine CLI stops responding after an amount of time.

Steps to reproduce:

  • Start the engine using <RE_HOME>/bin/karaf or <RE_HOME>/bin/trun.

  • Pair the engine (issue only occurs when paired).

  • Run Jobs or leave the engine idle. After a delay, the CLI hangs.

This issue is observed following the Karaf upgrade to version 4.4.7.

However, Only the CLI is affected. It does not occur when installing the engine as a system service using the installer. Regular engine functions, such as task execution, logging, and metrics, remain unaffected.

To resolve the hanging CLI issue, restart the engine after pairing to restore access to the Karaf console.

SSL error An SSL error occurs during data integration task deployment when all of the following conditions are met:
  1. Use the installer to install Talend Remote Engine.
  2. During installation, select Install as a system service.
  3. During installation, select Use SSL for JobServer communication to enable SSL automatically.
  4. Start Talend Remote Engine using the shell scripts from the bin folder.
  5. Run data integration tasks with the engine.

Task execution fails with an error message similar to the following:

Execution 8720a57b-d454-420d-b894-ba768f8a24c4 failed with code -1 and \
error org.talend.remote.commons.exception.ClientServerException: \
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure               

This occurs because the automated SSL setup for a Talend Remote Engine service is not designed to be used with the shell scripts.

To avoid this issue, do not use the shell scripts to start the engine service, use the usual way instead:
  • On Windows, use its services management console, services.msc, or run the command net start Talend-Remote-Engine.
  • On Linux, run the command systemctl start talend-remote-engine.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!