Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
LisaHourmand
Contributor
Contributor

Talend - Snowflake and MySQL tSetKeystore issue

Hi,

In Talend Cloud, I have a job with a connection to two databases:

  1. Snowflake connection using key pair authentication
  2. MySQL connection using user and password authentication

Technical details:

  • I'm using a tSetKeystore component to store the private key file in the prejob
  • The current configuration causes connection issues when components are ordered as: tSetKeystore -> tDBConnection (Snowflake) -> tDBConnection (MySQL)
  • When I change the order to: tDBConnection (MySQL) -> tSetKeystore -> tDBConnection (Snowflake) The job works successfully.

My hypothesis is that the tSetKeystore component modifies JVM parameters, which interferes with the MySQL connection. To validate this:

  • If I isolate the connections in separate subjobs, the connection fails
  • Clicking "Use an independent process to run subJob" resolves the issue by resetting JVM parameters

Questions:

  1. Can you provide a solid explanation for why JVM parameters affect the MySQL connection?
  2. Is there a clean way to launch the job without changing the component order?

The current workaround is suboptimal, as it would require establishing a MySQL connection at the job's beginning, potentially maintaining an unnecessary long-running database connection.

Would you like me to make any further modifications to the request?

Labels (1)
  • Cloud

1 Solution

Accepted Solutions
quentin-vigne
Partner - Creator II
Partner - Creator II

Hello @LisaHourmand 

My guess is that since tSetKeyStore sets values for javax.net.ssl properties, it affects the components that follow.

Most recent MySQL versions use SSL connections by default.

Since the Java SSL environment has been modified, the MySQL JDBC driver inherits these changes from tSetKeyStore, which can impact the connection.

If possible, try adding the following parameter to the Additional Parameters section:

useSSL=false

This will disable SSL if your connection allows it.

Have a great day!

 

- Quentin

View solution in original post

1 Reply
quentin-vigne
Partner - Creator II
Partner - Creator II

Hello @LisaHourmand 

My guess is that since tSetKeyStore sets values for javax.net.ssl properties, it affects the components that follow.

Most recent MySQL versions use SSL connections by default.

Since the Java SSL environment has been modified, the MySQL JDBC driver inherits these changes from tSetKeyStore, which can impact the connection.

If possible, try adding the following parameter to the Additional Parameters section:

useSSL=false

This will disable SSL if your connection allows it.

Have a great day!

 

- Quentin