DB connection pool size issue

[rishabhpoddar]

Even if we set server thread pool size and db connection pool size to 1, the core occasionally complains about not being able to get a connection even after 5 seconds:

io.supertokens.webserver.WebserverAPI.service(WebserverAPI.java:165) | javax.servlet.ServletException: io.supertokens.pluginInterface.exceptions.StorageQueryException: java.sql.SQLTransientConnectionException: SuperTokens - Connection is not available, request timed out after 5000ms.",
   "\u0001\u0000\u0000\u0000\u0000\u0000\u0000�07 Dec 2022 05:05:32:513 +0000 | ERROR | pid: 1f5cf52e-fa81-4cee-8948-da190eec0803 | [http-nio-0.0.0.0-8082-exec-1] thread | io.supertokens.webserver.WebserverAPI.service(WebserverAPI.java:165) | API threw an exception: POST /recipe/session/refresh"

This should really never happen given that both the connection and web server pool size is the same and each API uses one connection and releases it (unless there is a bug). We do have cronjobs that also use one connection each, but those connections should still be available after 5 seconds.

[govindraj111]

I mostly know the solution and would love to solve it for you. Assign me the issue.

[rishabhpoddar]

hey @govindraj111 could you please describe the solution before I assign it to you?