Prisma connection failing: Timed out fetching a new connection from the connection pool
Hello!
Trying to deploy a lambda function that's using a container image running my node code containing prisma.
When I hit any endpoint they will fail on reaching the database due to time out.
Already red the docs and my params look like this
sslmode=require&connect_timeout=15&connection_limit=20&pool_timeout=202 Replies
fascinating-indigo•14mo ago
Hey @JuanmaPedrozo,
Can you share the connection string and where's your database hosted?
generous-apricotOP•14mo ago
Hi! @Rishi Raj Jain Thanks for replying.
Sure I will provide you with that info.
This is my connection string. Will change the pass just in case. Let me know if you need it.
postgresql://task-tracker-db_owner:***********@ep-snowy-cake-a5vg3qdh.us-east-2.aws.neon.tech/task-tracker-db?sslmode=require&connect_timeout=15&connection_limit=20&pool_timeout=20
Additional info, maybe helpful. When I try to connect from my computer, I have no issue. I'm from Argentina and everything works fine.
Just when running that aws lambda, I get the Time out error or sometimes, the Cant reach database at ...e
Hi @Rishi Raj Jain I think we can close this post. I could fix my issue. Seems that I was missing one line of code that was preventing the app to execute in a proper way. I don't know how it was related to the time out error. Maybe some promise that was hanging or somethig.
But everything is working fine now. Thanks!