A talend job did run fine in the past two years, however, recently it was running slowly for several hours and freezes occasionally.

The job does not have much complicated sunjobs and it reads a file row by row, and for each row, checks the record type and sends the row to one of two possible output files. 

When trying to process a file with less than 30.000 lines, It loads about 1000 lines and then seems to freeze for several minutes, then loads another batch of lines, and so on. This issue doesn't reproduce on a newly created job (Duplicated one)

Resolution

After made an investigation on thread dump, the real time statistics was blocking the job and the problem seems to be appearing from the Statistics Monitor. It is suggested disable stats and logs both from Studio and Talend Administration Center sides using the below steps and re-run the job.

Studio Side

Disable Stats and Logs for Job level

Studio--> Designer -->Job-->Stats&Logs--> Disable the below check boxes.

• Use Statistics 
• Use Logs
• Use Volumetrics

We already have a global option in Studio >Preference>Talend>Run/Debug for Project Level

Talend Administration Center side

Job Conductor page--> Statistics-->disabled

Job won't open Socket and send message to Studio/Job Server when Statistics is disable and no matter disable it on job or project level, need to re-deploy jobs to Job server.

Cause

Checked the Thread dump and identified the below blocked threads:

org.talend.administrator.statistics.business.RealtimeTaskLoader->ExecStatisticsMonitor

The blocked threads indicate the problem occurs while retrieving the statistics and logs and the space and performance for this job is getting less and slower after it has been working for a while. 

Environment

• Talend Studio 
• Talend Administration Center 

When a user is deleted, any spaces, apps, scripts, and data connections they own will remain in the tenant without an owner. To prevent orphaned records, reassign ownership of these assets before deleting the user. Source: Reassigning ownership of spaces and resources (Qlik Cloud Documentation)

But even if the app is considered an Orphaned App, the owner can be changed in the Qlik Cloud Analytics Administration Console:

1. Open Qlik Cloud and open the menu
2. Access the Administration menu
3. Go to Content
   
   
   
   
4. Select the Apps tab
   
   
5. Filter by Deleted User in the Owner column
   
   
   
   Apps owned by Deleted Users will be listed.
   
   
6. Click the ... (ellipses) menu
   
   
   
   
7. Select Change Owner and change the ownership of the app

Environment

• Qlik Cloud Analytics

Executive Summary 

Security issues in Qlik Sense Enterprise for Windows have been identified, and patches have been made available. If the vulnerabilities are successfully exploited, these issues could lead to a compromise of the server running the Qlik Sense software, including unauthenticated remote code execution (RCE).

This issue was discovered by Qlik during internal security testing and no reports of it being maliciously exploited have been received.

Affected Software 

All versions of Qlik Sense Enterprise for Windows prior to and including these releases are impacted: 

• May 2024 Patch 9
• February 2024 Patch 13
• November 2023 Patch 15
• August 2023 Patch 15
• May 2023 Patch 17
• February 2023 Patch 14

Severity Rating 

Using the CVSS V3.1 scoring system (https://nvd.nist.gov/vuln-metrics/cvss), these issues are rated HIGH.

Vulnerability Details

(CVE-pending) QB-29918, QB-29750 Remote Code Execution (RCE) via Connectors

Severity: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H 8.8 (High)

Unprivileged users with network access may be able to create connection objects that trigger the execution of arbitrary EXE files on Qlik Sense Enterprise for Windows.

(CVE-pending) QB-29586, QB-29864, QB-29482, QB-29802 - Broken Access Control (BAC)

Severity: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H 7.5 (High)

Unprivileged users with network access to Qlik Sense for Windows installation may be able to execute remote commands that could cause high availability damages, including high integrity and confidentiality risks.

Resolution 

Recommendation 

Customers should upgrade Qlik Sense Enterprise for Windows to a version containing fixes for these issues. Fixes are available for the following versions:

• November 2024 Initial Release
• May 2024 Patch 10
• February 2024 Patch 14
• November 2023 Patch 16
• August 2023 Patch 16
• May 2023 Patch 18
• February 2023 Patch 15

All Qlik software can be downloaded from our official Qlik Download page (customer login required).

Question

What changes are made to the seat allocation after a license renewal?

If the number of seats or users will decrease after a license renewal, the admin user will receive an email that asks to de-allocate the exceeding seats within 14 days, and a reminder 7 days after. 
At the end of the 14 days, the seats will be de-allocated automatically starting from the least recent accesses. 
All of this info is included in the email received by the admin user.

Related Content

You can find further details on these seats allocation in tmc-account-license-info

Including details on what's considered admin seat within Talend Management Console.

Environment

Talend Cloud 

When using Kafka as a target in a Qlik Replicate task, the "Control Table" name in target is created in lower case, for example the Apply Exception topic name is "attrep_apply_exceptions"  (if auto.create.topics.enable=true is set in Kafka broker config/server.properties file), This is the default behavior. 

In some scenarios, you may want to use the non-default topic name or topic name in upper case etc to match the organization naming standards rule. This article describes how to rename control table topics' name.

In this article, we will use the topic name "attrep_apply_exceptions" as an example. You can customize below control topics using the same process:

• attrep_apply_exceptions
• attrep_status
• attrep_suspended_tables
• attrep_history

The same way works for more generic level , not only for Kafka target endpoint. In generic level we may rename other metadata eg "target_schema" too.

Resolution

1. Export the JSON of the task
   
    
   
2. Position to the line of the JSON file and identify the element "exception_table_settings"  (usually is empty, as below):
   
   "exception_table_settings": {
   },
3. Override the element to add the table_name attribute and SAVE the changes:
   
   "exception_table_settings": {
   "table_name": "CUSTOM_NAME_ATTREP_APPLY_EXCEPTIONS_TABLE"
   },
   
   In above sample, we rename the topic  exception_table_settings  name to CUSTOM_NAME_ATTREP_APPLY_EXCEPTIONS_TABLE (it's case sensitive, and in upper case).
   

   Kafka topic names cannot exceed 255 characters (249 from Kafka 0.10) and can only contain the following characters:

   a-z|A-Z|0-9|. (dot)|_(underscore)|-(minus) 

   More detailed information can be found at Limitations and considerations.

   The safest topic name length is 209 (rather than 255/249).

4. Import the JSON of the task
   
   After the import, The topic name shows in GUI is default name still, however the new topics name takes action, the task can be edited by using GUI freely until change the control topics name again by above steps.
5. Run the task.

Environment

Qlik Replicate  (versions 2022.11, 2023.5 and above)
Kafka target

Related Content:

         case #00010983, #00108779

Generate a record to attrep_apply_exceptions topic for Kafka endpoint

With the new inclusion of the Get Chart Image block in the Qlik Reporting connector in Qlik Application Automation, you now have more options to notify a group of users with more in-depth data and charts using Slack, Microsoft Teams, and email.

This article will guide you in sending your first chart image to Slack with Qlik Application Automation.

It explains a basic example of a template configured in Qlik Application Automation for this scenario.

You can make use of the template which is available in the template picker. You can find it by navigating to Add new -> New automation -> Search templates and searching for 'Send a Chart Image to Slack' or 'Embed a chart image in an email' in the search bar, and clicking the Use template option.

For guidance on sending charts via Microsoft Teams and mail, go to the "Next Steps" section at the end of this article.

You can download examples of the automations from this article: Send-chart-image-to-slack.json, Send-chart-image-to-outlook.json, Send-chart-image-to-mail.json, Send-chart-image-to-microsoft-teams.json

Full Automation

Configure the Automation

1. Open the automation editor and search for the Qlik Cloud Services connector on the left-hand menu.
   
   
2. Drag the blocks “Select Field Value” and “Create Bookmark” to the canvas and fill in the required inputs. You can add multiple Select Field Value blocks to apply selections to various fields. The Create Bookmark block is then used to create a temporary bookmark that can pass the selections to the Get Chart Image block.
   
   
   
   
   
   
   

   Warning: Whenever the “Get Chart Image” block is to be used, we advise you to only use it with temporary bookmarks or pre-existing persistent bookmarks.

2. Search for the Qlik Reporting connector on the left-side menu, then drag the "Get Chart Image" block to the editor and attach it below the previous block.
   
   Choose the same app you chose when creating the temporary bookmark and use the ID value received from the “Create Bookmark” block. 
   
   
   
   The height and width inputs are not required and default to 1000 if the fields are empty.
   
   Manually insert the Object ID input; it can not yet be retrieved through an API call.
   
   To find the chart ID from the app, open the app, then click Edit Sheet, right-click the chart, and open the Share/Embed menu from the menu dropdown that appears. You will see the object ID of the chart under the chart preview section as shown below:
   
   
   

    

3. Add the 'Condition' block to check whether the "Get Chart Image" block has returned a successful response.
   
   
   
   
   1. If the condition block outcome evaluates to true:
      
      
      • Search for Slack connector from the left-side menu, add the "Upload File To Channel" block, and fill in all the required inputs.
        
        
        
        
      • The chart image gets posted on the Slack channel as shown below:
        
        
         

   2.  If the condition block outcome evaluates to false:

      • Add the "Update Run Title" block to specify that the "Get Chart Image" block failed due to an error.
        
        
        
        
      • Add an "Error" block to throw an error message from the "Get Chart Image" block and set the current automation run to be in a failed state.
        
        
        

Configure and send the Output

Embed the chart in the email

Gmail does not support embedding base64 encoded images due to security constraints. To work around this, we advise sending the chart image as an attachment through the Send Mail block in the Mail connector if you use a Gmail account.

See Gmail blocking small embedded inline images in email template for details on the restriction. 

1. To embed the image in an email, you'll need to replace the Slack block with Send Mail block from the Microsoft Outlook 365 connector or the Send Mail block from the Mail connector and configure the block's Type parameter to HTML.
2. In the body of the HTML, start adding a <img> tag and set the src parameter of the img tag to "data&colon;image/png;base64,".
   

   
   

3. Add the Get Chart Image block output at the end of the src parameter.
   

   
   

4. Click the Get Chart Image label in the input parameter, and pick the Add formula option; then search for the "base64 encode" formula to apply it to the output from the Get Chart Image block.
   
   
   
   
   

   
   

5. Finalize the img tag with an optional width and height to style the image.
   
   

Send the chart to a channel in Microsoft Teams

1. To send the image to Microsoft Teams, replace the Slack block with the Send Html Message With Base 64 Image block from the Microsoft Teams connector.
2. Configure the "Base 64" parameter of the block by mapping it to the output of the Get Chart Image block.
   

   
   

3. Click the field mapping for the Get Chart Image again and open the formula picker. Search for the base64 encode formula and apply it.
   
   
   
   
    
4. Set the Image Content Type parameter to image/png and (optionally) provide additional HTML content that will be inserted before or after the image.
   

   
   

The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.

Environment

• Qlik Cloud 
• Qlik Application Automation 

Related Content

• Distributing Chart Images through Automation

This article explains how to simply set up JWT authentication using Qlik Sense default certificates and test it.

Steps:

1. Create a new virtual proxy
   
   This section only explains settings specific to JWT and supposes that you have set up Name, Prefix, Session cookie header name, load balancing nodes and linked a Proxy to the new virtual proxy.
   These are the minimum settings required for a virtual proxy to work correctly. Please refer to the Qlik Sense Online Help "Creating a virtual proxy" as well as Qlik Sense For Administrators - JWT authentication for details.
   
   
   1. In the authentication section, select JWT for authentication
   2. Paste the certificate used to sign/decrypt JWT in "JWT certificate
      
      In this article, we will use the default Qlik Sense certificate located:
      
      Important note: We use Qlik Default certificates for simplicity in this article, in a Production scenario, the customer should create the key material (generate a private/public key pair for JWT signing and verification) that is managed by customer internal security policies.
      
      
   3. Go to C:\ProgramData\Qlik\Sense\Repository\Exported Certificates\.Local Certificates
   4. Open server.pem in a text editor
   5. Copy the content including -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- then paste it in the JWT Certificate field in the QMC > Virtual Proxy configuration.
   6. Choose a value for JWT attribute for user ID and JWT attribute for user directory. That can be anything (except reserved key words for JWT claims) but it must match the values used in the JWT payload section when the JWT is generated.
   7. Apply changes and close.
      
       

      

      
      
      
2. Generate the JWT
   
   In this article, we will directly use the JWT debugger available on https://jwt.io to generate the token. In a real use case, the JWT library corresponding to the programming language used should be used to generate the JWT.
   
   
   1. Open https://jwt.io and go to the debugger
   2. Select RS256 for the algorithm
   3. In the PAYLOAD box, set up your attributes previously set via QMA in Qlik Sense's virtual proxy configuration for the user ID and the user directory. (Note: Swap 'DOMAIN' with the user's directory) 
   4. In the Verify signature, paste server.pem (Certificate) and server_key.pem (Private key) content in the appropriate fields. Those files are both located in C:\ProgramData\Qlik\Sense\Repository\Exported Certificates\.Local Certificates
   5. You can now copy the JWT generated in the left field and test it. This should look like:
      
      
      
      
3. Test the generated JWT
   
   In order to log in with JWT, you need to inject the JWT as a header. There are various extensions available depending on your browser in order to test this.
   
   In this example, we are using Chrome with Modheader.
   
   
   1. Install ModHeader from the Chrome Web Store
   2. Try to go to the hub:
      
                https://{your server name}/{prefix for JWT virtual proxy}/hub/
      
      
   3. You should get a 401 error: "Could not authenticate the request: Expected an authentication header." as no header has been provided.
   4. Go to ModHeader and set the following header:
      
             Header name: Authorization
             Header value: Bearer yourjwt
      
      
      
      
   5.    Reload the page, you should now be logged into the hub correctly.

In order to integrate your solution with Qlik Sense using JWT authentication, you will need to pass in your code the JWT token in the authorization token for the first request to Qlik Sense so that a session is created.

Related Content:

• Using Qlik Sense on Windows Repository API (QRS) with qlik-cli 
• Examples of integration for different purposes are available on the internet:
  https://github.com/qlik-oss/enigma.js/tree/master/examples/authentication/sense-using-jwt

It is not possible to set up a Microsoft Office 365 email provider with OAuth 2.0 authentication.
The HAR file shows this message in Network:

{connectionFailed: true, message: "Error during email request", success: false}
connectionFailed: true
message: "Error during email request"
success: false

Resolution

Configure the Mail.Send permission as it is described in Configuring a Microsoft 365 email provider using OAuth2.

Cause

This problem occurs when the Mail.Send permission has not been configured in the app registration.

Related Content

More information about the  Mail.Send permission can be found in Application permission to Microsoft Graph (learn.microsoft.com).

Environment

• Qlik Tabular reporting
• Qlik Cloud

The Replicate Connect Service does not start, leading to the Qlik Replicate IMS source endpoint failing to pull data from IMS.

Resolution

Verify what program is blocking irpcd.exe executable from launching, such as an anti-virus or threat protection program and enable an exception for irpcd.exe.

Cause

The irpcd.exe executable is quarantined by an anti-virus or similar threat protection program and cannot be started. 

Environment

• Qlik Replicate

Upgrading Qlik Data Transfer fails with the following error in the installation logs:

Something went wrong while upgrading Qlik DataTransfer. The following error appears in the log file: 0x80070570 = ERROR_FILE _CORRUPT

Resolution

1. Remove the damaged installation package (Qlik.DataTransfer.exe)
2. Download a new copy from the Qlik Download page
3. Verify the downloaded file's size on disk against the Size [MB] value on the download page
4. Stop all Qlike Data Transfer services
5. Right-click the newly downloaded Qlik.DataTransfer.exe and choose Run as Administrator
6. Run the upgrade 

If the installation still fails: 

1. Verify if any Anti-Virus or backup programs are blocking the execution of the file or updates to the existing files
2. Verify the integrity of your drives with, for example, chkdsk (Example command: chkdsk C: /f)
3. Run the upgrade

Cause

0x80070570 = ERROR_FILE _CORRUPT indicates a damaged or otherwise corrupt installation file. This can be caused by the file itself being damaged or an underlying issue with the file system.

Environment

• Qlik Cloud
• Qlik Data Transfer

Question I

Will the method to upgrade to Java 17 be the same as: upgrading-java-for-talend-remote-engine when a Remote Engine is already installed (from lower version like 8 or 11)?

The method is not the same for Java 17. Starting from Remote Engine version 2.13, it requires Java 17.
The document is only valid for Remote Engine versions 2.12 or lower. 
From Remote Engine versions 2.13 and up, it will be required to re-install the Remote Engine.
 

Question II

Will the method of setting up Java 17 in Talend Studio remain the same as: setting-compiler-compliance-level ?

The answer is YES .

Question III

How will Camel components in route be used?

It is a matter of dependency management. Once Studio will be upgraded to 8.0.1-R2025-02 (Java 17/Camel 4), any newly created routes or existing routes will depend on Camel 4 so 
appropriate libraries will be used at build/run time (either installed in Studio with update, or downloaded).
It is the same for all route components. It will be pretty transparent for the final user.

Question IV

Where is Camel 4 bundled?

Camel 4 libraries are either installed in Studio, or downloaded. OSGi features for Camel 4 are also pre-installed in Talend Runtime. 
Either users deploy routes as Microservices and Camel 4 dependencies are packaged in fat Jar at build time or users deploy in Talend Runtime and the container (which new version will be delivered in Feb. 2025) includes all pre-installed Camel 4 features.

Additionally, the Remote Engine has nothing to do with Camel 4.

Related Content

If you are looking for more information about Java 17 Migration Guide, please refer to this KB article

Qlik-Talend-Products-Java-17-Migration-Guide

Environment

Talend Cloud 

Route(OSGI-based) service design facing child Job bundle jar (child bundle was introduced by cTalendJob in Route design), encounters the error "Unable to resolve root : missing requirement" after being deployed to Runtime. However, Route runs smoothly in Studio debug run mode.

The Runtime logs provide insightful error messages as detailed below:

org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=TestBasicRoute-feature; type=karaf.feature; version="[0.1.0,0.1.0]"; filter:="(&(osgi.identity=TestBasicRoute-feature)(type=karaf.feature)(version>=0.1.0)(version<=0.1.0))" [caused by: Unable to resolve TestBasicRoute-feature/0.1.0: missing requirement [TestBasicRoute-feature/0.1.0] osgi.identity; osgi.identity=org.example.route.TestBasic; type=osgi.bundle; version="[0.1.0,0.1.0]"; resolution:=mandatory [caused by: Unable to resolve org.example.route.TestBasic/0.1.0: missing requirement [org.example.route.TestBasic/0.1.0] osgi.wiring.package; filter:="(osgi.wiring.package=@BundleConfigImportPackage@)"]]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.400.jar:?]

Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve TestBasicRoute-feature/0.1.0: missing requirement [TestBasicRoute-feature/0.1.0] osgi.identity; osgi.identity=org.example.route.TestBasic; type=osgi.bundle; version="[0.1.0,0.1.0]"; resolution:=mandatory [caused by: Unable to resolve org.example.route.TestBasic/0.1.0: missing requirement [org.example.route.TestBasic/0.1.0] osgi.wiring.package; filter:="(osgi.wiring.package=@BundleConfigImportPackage@)"]

at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.400.jar:?]

Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.example.route.TestBasic/0.1.0: missing requirement 

Cause

The child bundle JAR is lacking the 'lib' and 'osgi-info' folders. Additionally, the custom Maven files ('pom.xml', 'pom-parent.xml', 'pom-bundle.xml', and 'pom-feature.xml') are outdated, which contravenes the Studio's default dependency settings during the compilation and packaging processes.

Resolution

1. Open Project Settings in Talend Studio, then navigate to Build -> Maven -> Set custom scripts by folder -> Route Designs -> Routes -> Delete Maven files, remove the old Maven files: 'pom.xml', 'pom-parent.xml', 'pom-bundle.xml' and 'pom-feature.xml'.
2. Rebuild and republish the service design.

Environment

• Talend Data Integration 8.0.1

Updating an Excel Worksheet using Qlik Application Automation leads to Microsoft Excel reporting a 503 error.

Resolution

A 503 (Service not Available) error indicates the target system, in this case Microsoft Excel, cannot handle the calls due to high frequency. To overcome this, a retry mechanism would need to be implemented in your automation, adding robustness in front of those errors.

Attached to this article is a sample automation demonstrating how to handle these errors in the Excel block and implement retry logic when it fails.

Cause

Third-party bottleneck.

Environment

• Qlik Application Automation
• Qlik Cloud

TAC tasks are hanging on "Running" status for a long time in Job Server, and it does not end. 

Analysis

This issue can be identified by long duration of task execution time and it can be seen from the large time gap between the job end time and the task end time.

Usually, the time gap between the job end time and the task end time are small if there are no problems occurring.

Resolution

Please check and try the following points.

1. Check that the Talend Administration Center application (or service) is up and running.
2. Check that the connection can be established to the Job Server.
3. Check that there are no differences in the version of the Talend Administration Center and the Job Server, since the Talend Administration Center and the Job Server affect one another. If the version is old on either side, it may cause problems.
4. In order to reconnect Talend Administration Center and the Job Server, restart Talend Administration Center to see if it fixes the problem.

Cause

It is most likely that there are network connection issues (because of network infrastructure, VPN, etc)between the Talend Administration Center and the execution server (Job Server).
One possible situation may be the following: After the task is run by the Job Server, the execution result should be sent to the Talend Administration Center normally. If there is a connectivity problem between the Talend Administration Center and the Job Server, then the execution result will not be sent to the Talend Administration Center, which causes this problem.

Environment

Talend Administration Center 

You can access Qlik Sense demo apps from https://demos.qlik.com/.

If you are looking for real-life business examples, our Qlik Gallery hosts a platform meant for sharing apps, outcomes, and ideas. It is not restricted to Qlik-provided demos and mostly consists of customer examples.

If you are looking to download demo apps:

1. Go to https://demos.qlik.com/ 
2. Select Downloadable from the available Tags
   
3. Open the App
4. A Download button will be available (if logged in)
   
   

After upgrading to Qlik Sense Enterprise on Windows May 2023 (or later), the Qlik Sense Repository Service may cause CPU usage spikes on the central node. In addition, the central Engine node may show an increased average RAM consumption while a high volume of reloads is being executed. 

The Qlik Sense System_Repository log file will read:

"API call to Engine service was successful: The retrieved 'StaticByteSize' value for app 'App-GUID' is: 'Size in bytes' bytes." 

Default location of log: C:\ProgramData\Qlik\Sense\Log\Repository\Trace\[Server_Name]_System_Repository.txt

This activity is associated with the ability to see the Base memory size in the Qlik Sense Enterprise Management Console. See Show base memory size of apps in QMC.

Resolution

The feature to see Base memory size can be disabled. This may require an upgrade and will require downtime as configuration files need to be changed.

Take a backup of your environment before proceeding.

1. Verify the version you are using and verify that you are at least on one of the versions (and patches) listed: 
   
   
   • May 2023 Patch 13
   • August 2023 Patch 10
   • November 2023 Patch 4 
   • February 2024 IR
     
2. Back up the following files:
   
   
   • C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
   • C:\Program Files\Qlik\Sense\Repository\Repository.exe.config
     
     *where C:\Program Files can be replaced by your custom installation path.
     
     
3. Stop the Qlik Sense Repository Service and the Qlik Sense Dispatcher Service
   
4. Open and edit the capabilities.json with a text editor (using elevated permissions)
   1. Open C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
   2. Locate: "enabled": true,"flag": "QMCShowAppSize"
   3. Change this to: "enabled": false,"flag": "QMCShowAppSize"
   4. Save the file  
5. Open and edit the repository.exe.config with a text editor (using elevated permissions)
   1. Open C:\Program Files\Qlik\Sense\Repository\Repository.exe.config
   2. Locate: </appSettings>
   3. Before the </appSettings> closing statement, add:
      <add key="AppStaticByteSizeUpdate.Enable" value="false"/>
   4. Save
6. Start all Qlik Sense services
7. Verify you can access the Management Console

If any issues occur, revert the changes by restoring the backed up files and open a ticket with Support providing the changed versions of repository.exe.config, capabilities.json mentioning this article. 

Related Content

Show base memory size of apps in QMC

Internal Investigation:

QB-22795
QB-24301

Environment

Qlik Sense Enterprise on Windows  May 2023, August 2023, November 2023, February 2024. 

When using Qlik Sense behind a reverse proxy, environment.user.ip is always the IP of the reverse proxy instead of the end user client.

Environments:

• Qlik Sense Enterprise for Windows

This is a product limitation.

A feature request (SHEND-225) has been logged but there is no information if and when the feature will be implemented yet.

Unable to Execute Talend job query after Talend Remote Engine and JAVA version 17 upgrade in PROD.

The Same query was running fine before on Java 11 version but after Java upgrade to 17,  it is unable to run the particular query and same jobs are failing due to below error

The original query inside hive tDBInput component has no grammar issue.

Execution failed with code 1 and error Job stopped with errors or unable to run. Exception in component tDBInput_4 (Outbound_File_Creation_Type_1) org.talend.sdk.component.api.exception.ComponentException: (java.sql.SQLException) [Amazon][HiveJDBCDriver](500051) ERROR processing query/statement. Error Code: 40000, SQL state: TStatus(statusCode:ERROR_STATUS, infoMessages:[*org.apache.hive.service.cli.HiveSQLException:Error while compiling statement: FAILED: ParseException line 1:3328 missing EOF at 'JOIN' near ')':17:16, org.apache.hive.service.cli.operation.Operation:toSQLException:Operation.java:335, org.apache.hadoop.hive.ql.reexec.ReExecDriver:compileAndRespond:ReExecDriver.java:126,

Resolution

Try the setting "UseNativeQuery=1" in JDBC connection URL property to enable the use of Native query option.

For example:
jdbc:hive2://localhost:10000/foundation;AuthMech=2;UseNativeQuery=1

This parameter specifies whether the driver transforms the queries emitted by applications. 

1: The driver does not transform the queries emitted by applications, so the native query is used. 

0: The driver transforms the queries emitted by applications and converts them into an equivalent form in HiveQL.

If the application is Hive-aware and already emits HiveQL, then enable this option to avoid the extra overhead of query transformation.

Cause

As HiveQL is using parameter "UseNativeQuery=0" by default, which means it will transform query inside JDBC before sending to HS2 , and the introduced false optimization query will cause the problem. 

Environment

Talend Big Data 

Qlik Replicate tasks using DB2 LUW Source Endpoint experience latency when consuming data.

Resolution

Verify if the DB2 LUW configuration for the DB2 instance of the Source endpoint has its configuration parameters LOGMETHOD1 and LOGMETHOD2 set to a backup device location.

This would indicate the DB2 Log Reader Agent is loading the transaction logs from a backup device which will add overhead to the task using this DB2 Source Endpoint.

To correct the condition you can set the DB2 parameter by the DBA Overflow Log path from NULL to archive_log_path. See overflowlogpath - Overflow log path configuration parameter for more information.

This path can point to a local disk on the DB2 server for optimal access to the DB2 transaction logs.

First log archive method:

(LOGARCHMETH1) = VENDOR:/opt/simpana/Base64/libDb2Sbt.so

Second log archive method:

(LOGARCHMETH2) = DISK:/db2/P10/alternate_logpath/

Overflow log path:

(OVERFLOWLOGPATH) = archive_log_path

Cause

This is the result of the DB2 Log Reader Agent, which Qlik Replicate calls using the DB2 API and from which we access the transaction logs from DB2. In a setup in which LOGMETHOD1 is pointing to a backup device, the DB2 Log Reader Agent loading the transaction logs will lead to overhead and ultimately latency. 

Related Content

• overflowlogpath - Overflow log path configuration parameter

Environment

• Qlik Replicate