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

Announcements
Qlik Connect 2026! Turn data into bold moves, April 13 -15: Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
jchen
Contributor III
Contributor III

need help with connection to MongoDB

Hi, Need some help.

I am getting exception error while trying to connect MongoDB using tMongoDBConnection component from Talend Open Studio for Big Data 7.2.1.

com.mongodb.MongoTimeoutException: Timed out after 30000 ms while waiting to connect

I was able to connect on the same machine via MongoDB Compass and NoSQLBooster.

Any troubleshooting tips would be appreciated.

Thanks,

Jun

Labels (2)
14 Replies
jchen
Contributor III
Contributor III
Author

No, I don't. I will try to get one. So, do I need to use the tSetKeystore since this is a SSL connection? Thanks!

 

 

Anonymous
Not applicable

Hello,

To connect to the HTTPS URL of a non-public server, you must provide the Talend Job or Talend server with the SSL certificate file of the server you are trying to connect to.

 

Connecting to various public servers, such as GitHub or Microsoft, is often easy (that is, you do not have to do any special configuration) because your browser and your Job can check the validity of those servers' SSL certificates with a public certificate authority.

 

However, if you are trying to connect to a non-public server such as your internal Jira server; for example, jira.mycompany.com, that server's SSL certificate is not known to the public certificate authorities, so you need to configure your Job or Talend server to trust that SSL certificate, and therefore trust that Jira server.

For more information, see the Java67 article, Difference between trustStore vs keyStore in Java SSL.

Best regards

Sabrina

jchen
Contributor III
Contributor III
Author

Hi,

 

I got the keystore and trustore files. I have setup as shown in attach. Is this correct? I am still getting the same error. Please help.

 

thanks,

Jun

jchen
Contributor III
Contributor III
Author

the issue was resolved. it was caused incorrect certificate. thank you for your help.

Anonymous
Not applicable

Hello,

Thanks for your feedback and letting us know it is resolved by yourself.

Best regards

Sabrina