TPS-4654-RT (cumulative patch) - 7.1

Introduction

This patch is cumulative. It includes the previous generally available patches from Talend ESB Runtime 7.1.1.

NOTE: To download this patch, liaise with your Support contact at Talend.

Fixed issues

This patch contains the following fixes:

TESB

• TPS-4654: [7.1.1] NPE 'org.apache.karaf.features.internal.service.FeaturesServiceImpl.getRepositoryClosure' when removing feature (TESB-29402)
• TPS-3320: [7.1.1] Timeout when trying to connect to JMX port 8888 (TESB-26434)
• TPS-2984: [7.1.1] Swagger UI not displayed (TESB-25111)
• TPS-2828: [7.1.1] Talend 7.1.1 - SSH issue connecting to karaf (TESB-24169)
• TPS-2822: [7.1.1] Not possible to use Event Monitor if SAM Server not started (TESB-24308)

TPSVC

• TPS-3653: [7.1.1] The connection from TAC to Runtime has been permanently lost (TPSVC-12684)
• TPS-3465: [7.1.1] When contexts are used in a DB component for connection fields and then published to nexus3, the job fails with a connectivity error in TAC. (TPSVC-8790) - Talend Runtime
• TPS-3138: [7.1.1] CreateProcess error=206, The filename or extension is too long (TPSVC-6838)
• TPS-3033: [7.1.1] When contexts are used in a DB component for connection fields and then published to nexus3, the job fails with a connectivity error in TAC (TPSVC-8790)
• TPS-2887: [7.1.1] JobServer connection from JobServer side (TPSVC-6981)

Prerequisites

Consider the following requirements for your system:

• Talend ESB Runtime 7.1.1 must be installed.

• Depending on the product, {container} is Talend-ESB-V7.1.1/container/ or Talend-Runtime-V7.1.1/

• Only in case that you have custom changes made in {container}/etc/org.talend.remote.jobserver.server.cfg, you need to backup this file and then copy it back after the patch is applied

• Current patch must be installed together with TPS-3669 for Talend Administration Console

Installation

Container

New Container (never started)

• Extract & replace the content of ZIP directory container into {container} directory

Structure after extract & replace should be :

{container}
├───bin     : existing dir
├───deploy  : existing dir
├───etc     : existing dir superseeded by patch
├───...
├───patches : dir from current or previous patch
│   └───Patch_20210212_TPS-4654_v1-RT-7.1.1
│           patch.bat
│           patch.commands
│           patch.sh
├───system  : existing dir superseeded by patch
│   ├───... : existing dir
│   ├───... : directories from patch
├───...

Existing Container

• Start Runtime Container
• Extract & replace the content of ZIP directory container into {container} directory

Structure after extract & replace should be :

{container}
├───bin     : existing dir
├───deploy  : existing dir
├───etc     : existing dir superseeded by patch
├───...
├───patches : dir from current or previous patch
│   └───Patch_20210212_TPS-4654_v1-RT-7.1.1
│           patch.bat
│           patch.commands
│           patch.sh
├───system  : existing dir superseeded by patch
│   ├───... : existing dir
│   ├───... : directories from patch
├───...

• Ensure username/password are right in {container}/patches/Patch_20210212_TPS-4654_v1-RT-7.1.1/patch.bat or {container}/patches/Patch_20210212_TPS-4654_v1-RT-7.1.1/patch.sh

  ... -u {username} -p {password} -f patch.commands ... 
  

• Execute {container}/patches/Patch_20210212_TPS-4654_v1-RT-7.1.1/patch.bat or {container}/patches/Patch_20210212_TPS-4654_v1-RT-7.1.1/patch.sh

• Ensure directory {container}/patches/Patch_20210212_TPS-4654_v1-RT-7.1.1/ contains new log files :
  • xxx-installation.log: patch installation log
  • xxx-init.log: state before patch installation
  • xxx-installed.log: state after patch installation