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

Announcements
Write Table now available in Qlik Cloud Analytics: Read Blog
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 Sabrina,
I just got an answer from MongoDB support regarding this exception:
The exception you are seeing is from the Java driver and usually occurs if the application has disposed or otherwise closed the connections in the pool, and then the application attempts to use said pool. You do not get this exception from having a connection pool that is too small.
This is really weird because as you can see in this screenshot the exception occurs during the connection, at the very first step of each job:
0683p000009MBqk.png
It happends randomly and under some load, but never more than 30 concurrent connections so it should be handled correctly.
Thanks for any help,
Maxime.