SSL TrustStore Conflict when combining WebService and tSendEmail in one job

[thuhuyen89]

I am facing an issue with SSL truststores in my Talend job and would appreciate advice:

My main job has two parts:

The WS part using tSoap with its own isolated truststore configured directly in the component's SSL settings.

The tSendEmail at the end of the job which requires a different truststore

The problem is:

• When I run these two parts separately by disabling another, they both run successfully.

• But when I both activate them, I get the following error.

So, does Talend share JVM SSLContext across components even when tSOAP has its own truststore configured?

Thank you

[gouravdubey5]

Hello,

Yes, this behavior is expected.

Talend components run within the same JVM, and SSL configuration (truststore / keystore) is handled at the JVM level, not per component. Even though tSOAP allows configuring a truststore in the component settings, internally it still relies on the JVM SSLContext.

When multiple components (such as tSOAP and tSendEmail) require different truststores, the last initialized SSL configuration can override the previous one, which leads to SSL conflicts when both parts of the job are executed together.

Key points:

Talend does not support multiple truststores simultaneously within a single JVM.

Component-level SSL settings do not fully isolate SSL contexts.

This is why each part works independently, but fails when executed together.

Supported workarounds:

Use a single consolidated truststore containing all required certificates.

Split the logic into separate jobs and execute them sequentially.

Launch separate JVMs (for example, via tRunJob with “Use an independent process” enabled).

Externalize one of the operations (e.g. email or SOAP call) to a separate service or job.

Best practice:
Always standardize SSL configuration at the JVM level for a job and avoid mixing multiple truststores within the same execution.

Thanks,

Gourav