Skip to main content Skip to complementary content

Application Integration: known issues and known limitations

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

Studio

Limitation	Description	Available in
Java PSU not supported	Talend Studio 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: http://www.oracle.com/technetwork/java/javase/cpu-psu-explained-2331472.html	All Talend products with ESB
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 http://ws-i.org/deliverables/basicprofile.html. Other WSDL documents might also work but they are more likely to fail.	All Talend products with ESB
The Activity Monitoring Console as provided in Talend 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 Talend 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 tStatCatcher 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 Listening 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 Talend Studio, which means Jobs called by cTalendJob are not supported to use these components at all. Note that you can use the AMC perspective in Talend Studio for ESB 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).	All subscription-based Talend products with ESB
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).	All Talend products with ESB
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.	All Talend products with ESB
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.	All Talend products with ESB

Issue	Workaround	Available in
Route Builder beans cannot be organized in packages 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.	None	All Talend products with ESB
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.	All Talend products with ESB
Modifications to components in the source Route are not propagated to test cases 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.	All Talend products with ESB
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.	All subscription-based Talend products with ESB
Using the cTalendJob inside a Routelet is not supported.	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.	All subscription-based Talend products with ESB

Runtime

Limitation	Workaround	Available in
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 LogServer, see the article about How to disable the display of log events on the Logging page of Talend Administration Center.	All subscription-based Talend on-premises products with ESB
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.	All subscription-based Talend on-premises products with ESB

Issue	Workaround	Available in
OSGi Container fails to log messages that were sent to system.err / system.out 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.	All Talend products with ESB

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!

Leave your feedback here