TPS-2650 - 7.0

author
Talend Documentation Team
EnrichVersion
7.0
EnrichProdName
Talend ESB
EnrichPlatform
Talend ESB

TPS-2650

Info Value
Patch Name Patch_20190730_TPS-2650_v2_7.0.1
Release Date 2019-07-31
Target Verson 20180411_1414-7.0.1
Product affected Talend ESB Runtime

Introduction

This patch is cumulative and includes few previous patches.

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

Fixed issues

This patch contains the following fixes:

  • TPS-2650: [7.0.1] AMQ with master and slave broker, shutting down slave causes dead-lock (TESB-23118)

This patch also includes or supersedes the following patches:

  • TPS-2635: [7.0.1] Blueprint error: "name is already instanciated as null and cannot be removed (TESB-22943)
  • TPS-2511: [7.0.1] Route deploying: No native code clauses found in the value of Bundle-NativeCode (TESB-21976)
  • TPS-2516: [7.0.1] ClassNotFoundException when enabling FastJobInvocation in cTalendJob(TESB-22220)

Prerequisites

Consider the following requirements for your system:

  • Talend ESB Runtime 7.0.1 must be installed.

Installation

Installing the patch manually

A. Patch a new runtime installation which has never been started:

  1. Copy&Replace directory "system" from the present patch with all sub-directories and files into your "$Runtime_Home" directory (the one which contains "system" among other sub-directories). You will replace files "activemq-karaf-5.15.2-features-core.xml", "apache-camel-2.20.1-features.xml", "apache-cxf-3.2.4-features.xml", and "features-7.0.1.xml" (in sub-directories of "system").
  2. Start the Karaf container. The patch is effective from the beginning.

B. Patch a runtime installation which is already in use:

  1. The patch can be applied while the container is running - container re-start is recommended after the patch has been applied as explained below.
  2. During the whole patching procedure, the ActiveMQ broker must not be running in slave mode. It is therefore recommended to make sure that feature "activemq-broker" uninstalled while the patch is applied. Execute this command before starting the application of the patch:
     karaf@trun> feature:uninstall activemq-broker
    
  3. Copy&Replace directory "system" from the present patch with all sub-directories and files into your "$Runtime_Home" directory (the one which contains "system" among other sub-directories). You will replace files
     "activemq-karaf-5.15.2-features-core.xml",
     "apache-camel-2.20.1-features.xml",
     "apache-cxf-3.2.4-features.xml", and
     "features-7.0.1.xml" (in sub-directories of "system").
    
  4. Start the Karaf container if it is not running.
  5. Go to the Karaf console and enter the following commands:

     karaf@trun> feature:repo-refresh
     karaf@trun> feature:uninstall camel-talendjob
     karaf@trun> feature:uninstall activemq-client
     karaf@trun> feature:uninstall camel-blueprint
     karaf@trun> feature:install camel-talendjob
     karaf@trun> feature:install activemq-client
    

    The commands may show error messages, success is tested in the following steps.

  6. For checking the update of activemq-osgi (TESB-23118), enter the following command:

     karaf@trun> list -s -t 0|grep activemq-osgi
    

    This command should show bundle "org.apache.activemq.activemq-osgi" of version 5.15.2.tesb1.

  7. For checking the update of camel-blueprint (TESB-22943), enter the following command:

     karaf@trun> list -s -t 0|grep camel-blueprint
    

    This command should show bundle "org.apache.camel.camel-blueprint" of version 2.20.1.tesb1.

  8. For checking the update of camel-talendjob (TESB-22220), enter the following command:

     karaf@trun> list -s -t 0|grep camel-talendjob
    

    This command should show bundle "camel-talendjob" of version 7.0.1.tesb1.

  9. If required, the "activemq-broker" feature can be installed again now. Furthermore, it is recommended to shut down and re-start the container.