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

Announcements
Qlik GA: Multivariate Time Series in Qlik Predict: Get Details
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Can't connect to mongo: pool is closed

Hi,
We are migrating from MySQL to MongoDB, using the exact same jobs, changing only connections/inputs/outputs components.
When running in our production cluster we randomly get this exception from the tMongoDBConnection component:
java.lang.IllegalStateException:The pool is closed

How can we handle this error?
Thanks,
Maxime.
Labels (3)
10 Replies
Anonymous
Not applicable
Author

Hi,
Could you please post your current job design screeshots into forum(migrating from MySQL to MongoDB)? Have you tried to check out "Die on error" option on tMongoDBOutPut component to see if there is any more error message printed on console?
Best regards
Sabrina
Anonymous
Not applicable
Author

Hi Sabrina, thanks for the answer,
Actually the problem is not occuring within talend, if I run any job within talend it runs fine. It looks like more a scalability issue:
If I run various jobs in parallel in our cluster then the connection problems appear, never in the Talend console. They always appear during the connection ( tMongoDBConnection  ), which is the first component of each job.
This is what our log tables looks like:
0683p000009MCIh.png
Anonymous
Not applicable
Author

Hi,
Could you please indicate the build version you are using? subscription solution?
Best regards
Sabrina
Anonymous
Not applicable
Author

Yes sure, we are using Talend Open Studio Big Data 5.6.2 
Anonymous
Not applicable
Author

Hi,
Have you tried to use tMongoDBClose in your workflow to close a connection to the MongoDB database?
Best regards
Sabrina
Anonymous
Not applicable
Author

Hi Sabrina,
Yes, every job starts with a tMongoDBConnection and ends with a tMongoDBClose.
Anonymous
Not applicable
Author

Hi,
Would you mind uploading your current job design screenshot into forum?
Best regards
Sabrina
Anonymous
Not applicable
Author

Yes of course, please find attached one example. All our jobs are designed the same way, regarding the connections. When we were working with MySQL the jobs were identicals and we didn't have this problem.
0683p000009MCBd.png
Anonymous
Not applicable
Author

Hi Sabrina,
Do you have any thoughts about this that could help me find the root of the problem?
Thanks a lot,
Maxime