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

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Kaszanka
Contributor III
Contributor III

SSL exception thrown on server, but not localy in studio

Hello,

 

I'm facing weird issue where my Job works fine when launched localy from Talend ESB studio on the server machine, but after deployment it throws:

org.apache.cxf.interceptor.Fault: Could not send Message.

Caused by: javax.net.ssl.SSLException: SSLException invoking https://test.salesforce.com/services/Soap/u/42.0: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

Caused by: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

Scenario was working fine yesterday (deployed). It's failing on tESBConsumer. Throwing the same result on previous version of that job as well (this version was working without any problems for at least two weeks now). Server machine runs windows server 2016 with Java in version 1.8.0_171.

 

Thanks in advance for any tips which will help me to at least track the root of my problem.

 

Labels (3)
14 Replies
Kaszanka
Contributor III
Contributor III
Author

Issue is now resolved with support portal help.
Anonymous
Not applicable

Hello,

Would you mind sharing some solution with us on forum?

Best regards

Sabrina

Kaszanka
Contributor III
Contributor III
Author

Sure,

Simmilar problems should be resolved with manual creation of configuration files and cert stores for your partner's endpoints. You can put cert store anywhere, configuration file has to be a copy of runtime/etc/org.apache.cxf.http.conduits-common.cfg

Just copy the file, replace "common" with your own suffix and edit "url", "tlsClientParameters.trustManagers.keyStore.file", "tlsClientParameters.keyManagers.keyStore.file" and passwords if necessary.

Regards,

Michał

pcristi
Contributor
Contributor

After 3 years I faced the same problem. I fixed it creating a folder called 'CERTS' at my user and into this folder I inserted the certificate (talendfsr.jks).

You should edit the file 'Talend-Studio-win-x86_64.ini' inserting the following

the info:

 

-Djavax.net.ssl.trustStore=C:\Users\priscila\CERTS\talendfsr.jks

(you should change for the folder and path you created)

 

This was enough to connect with the server and solve the problem 🙂

 

 

Anonymous
Not applicable

Hello,

Here is a KB article about: https://community.talend.com/s/article/Three-ways-to-set-a-truststore-for-an-SSL-TLS-connection-in-a...

Hope it helps.

Best regards

Sabrina