ESB: known issues and known limitations - 7.2

Talend Data Fabric Release Notes

English (United States)
Talend Data Fabric
Installation and Upgrade
Release Notes

We encourage you to consult the JIRA bug tracking tool for a full list of open issues:

All ESB use cases (Routes, REST and SOAP Data Services) require Java 8.




By default, macOS Sierra sets all downloaded files to "quarantine". This prevents you running the Studio.
  1. Unzip Talend Studio as usual.
  2. Open a Terminal window on the folder where you unzipped your Talend Studio.
  3. Execute either of the following commands: xattr -d * or xattr -c *
  4. Launch Talend Studio as usual.
Users with a recent version of Mac OS X may need to update their Gatekeeper settings to install Talend products. Gatekeeper is available from OS X 10.7.5.
  1. Click the Apple icon, and then click System Preferences.
  2. Under System Preferences, click Security & Privacy.
  3. Under Security & Privacy, click General tab.
  4. Click the lock icon next to Click the lock to make changes, and then identify yourself using the user name and password for an account with administrator rights. Only administrators can change the security settings.
  5. Under Allow apps download from, select the Anywhere radio button then confirm your choice in the dialog box that opens.
  6. Close all windows, so that your Mac automatically locks the Security & Privacy settings for you again.
  7. Install Talend Studio (or whatever other executable you want to install) by following the usual installation procedure. Note that, when you double click the file, you will see a warning saying that it is an application downloaded from the Internet, but if you click Open, your Mac should let you install it without further issues.
  8. Once you have completed the installation process, you can repeat the above steps to return your Security & Privacy settings to their previous value if you want.
Custom Installation of Talend Runtime and Job-Server on the same server might cause port conflicts [TUP-832]

If you install Talend Runtime and Job-Server as Service on the same machine, you need to make sure that you change the Job-Server port of the standalone Job-server. Otherwise these ports will be in conflict with the Job-Server included in Talend Runtime, which uses the same default ports as the standalone Job-Server.

As a workaround, consider first if you really need the standalone Job-Server, the Talend Runtime (which also includes a Job-Server, for DI use only), or if you need both on the same machine. Only in the last case you should make sure that you use other port during the setup for the standalone Job-Server (a configuration page is shown during installation).




Java PSU not supported Talend is only supported on Java CPU Versions, not Java PSU.

Some users reported problems using Talend Studio with Java PSU versions (such as jdk8_u92), but when reverting to a Java CPU Version (such as jdk8_u91) the problem was resolved.

See also:

Only WS-I Basic Profile compliant WSDL documents are supported All WSDL service descriptions should be at least WS-I Basic Profile compliant if you want to use them in Talend Studio. See Other WSDL documents might also work but they are more likely to fail.
The Activity Monitoring Console as provided in the Studio and the related Dashboard screens can be used to visualize tLogCatcher, tStatCatcher and tFlowMeterCatcher events. In Talend Enterprise ESB there are some limitations that you need to consider for these components and the related features in the Studio.
  • tLogCatcher can be used in Data Services and Jobs, but the tLogCatcher component must be explicitly included in the Job and the use of a database for logging is recommend in this environment (Talend Runtime - OSGi Container).
  • tStatCatcher (including the use of the tStaCatcher option provided in the Advanced Settings of some Components) and tFlowMeterCatcher can be used only in Jobs which are not defined as Keep Listening but not in Data Services (where the operations are implemented in Keep Listing Jobs). Also these components must be explicitly included in the Job and the use of a database for logging is recommended in this environment (Talend OSGi container).
  • tLogCatcher, tStatCatcher and tFlowMeterCatcher by the entire Activity Monitoring Console feature cannot be used within Routes developed using the Route designer with the Studio, which means Jobs called by cTalendJob are not supported to use these components at all.
  • Note that you can use the AMC view in Talend Enterprise ESB Studio but the related AMC Web-Console in TAC is only provided with a license which contains the DI Product (for example, Talend Platform for Data Services license).
tWaitForXXX components are not supported in Talend ESB Data Services and tRoute Jobs The tWaitForFile, tWaitForSqlData and tWaitForSocket components are not supported to be used in ESB Data Services (REST&SOAP) or in tRouteInput based Jobs (cTalendJob use cases).
tRunJob is supported with limitations The tRunJob component is supported with limitations, which means that only S4 (Minor) support cases are accepted and no patches are provided. If you use tRunJob within Data Services and Routes (with cTalendJob), support is provided on a "best effort" basis only. In most cases, there are class loading issues which can sometimes be resolved but not always.

This is because tRunJob is not designed to work in a Service/Route style (ESB) deployment, so regular support is not provided if you decide to use it, even though it may work in many cases. If you used tRunJob in the past, it is recommended to change your Job Design to use Joblets instead.

For DI and non-ESB use cases, it is still a valuable component and will have full support as before.

Additionally, the Use dynamic job option is not supported within ESB Routes or Data Services at all.

tParallelize does not work with Data Services Jobs and Routes The tParallelize component is designed for Data Integration Jobs. Do not use it in the context of Data Services Jobs and Routes because it is not thread safe between parallel requests and will cause huge memory and CPU consumption. Use a Route if parallel processing is a requirement.



Route Builder beans cannot be organized in packages [TESB-3701]

Beans in a route build can be used to add Java code for the route builder routes, however all beans are currently located in one single package.

XML payload content is not fully displayed in trace or debug mode

When starting a Data Service Job in trace/debug mode, the content of the Document fields of the flows is not displayed fully - only the first line of the XML payload is shown.

If you need to see the XML data you can place a tLogRow component anywhere in your models. Keep in mind that Talend Studio also allows you to disable this component, so that you can enable it for testing inside Talend Studio, but disable it for export or publishing.
Modifications to components in the source Route are not propagated to test cases [TESB-17405]

When you change the configuration of a component in a Route, the changes are not propagated to the related Route test cases automatically.

You can close the test case and reopen it to get the changes in the components propagated in the test case.
Filter can be applied with the CI for ESB to limit the Data Services and Routes which get built and deployed by the CI Builder maven plugin. Nevertheless when a Route uses cTalendJob, it will only work in case the Job and the Route are both part of the filter (criteria).

A recommendation would be to name the Job(s) with the same name as the Route with any extra details after the Route name. By this, the Route and the Job(s) would have the same starting name and would apply to a filter on this partial name. Alternative you can build the entire project where this limitation would also not exists.

Routelets does not support cTalendJob to be used inside a Routelet.

As Routelets are more optional in nature (still important for some use cases), it is recommended to limit the Routelet to the parts where a cTalendJob call is not required and to add the cTalendJob part to the main Route(s). If this is not possible then the only good workaround is to give up on Routelets and either

a) Add the Routelet parts again into each Route

b) Model the Routelet as a Route using a cVM Endpoint. Then the primary Route and this supporting Route need to be deployed to the Talend Runtime as two individual Routes (firstly the supporting Route which was a Routelet before, and then the primary Route(s) which use the supporting one). This workaround only works for OSGi Deployment to Talend Runtime but not for Microservice deployment as one Microservice is one Route currently. In the case of Microservice deployment, a Socket, JMS, or REST communication would be required.




When using Talend-LogServer, by default, event logs are stored without specific security protection and as such all logs are visible to anyone with access to the server (via an HTTP URL within your network). For information on how to deactivate the Talend Administration Center Logging Screen and Talend Log Server, see the article about How to disable the display of log events on the Logging page of Talend Administration Center on Talend Help Center (
OpenID authentication only supports usernames in lower case. If the username contains capital letters, Talend STS (Security Token Service) will throw an exception that the user is not found. If you want to use OpenID authentication, the username must be all in lower case.



OSGi Container fails to log messages that were sent to system.err / system.out [TESB-11603]

In the tesb.log file you will not see any messages which were sent via system.err or system.out.

If you encounter this issue, you can run the same scenario in Console mode as the system.err and system.out will show up on the console.