https://www.prisma.io/ logo
Join SlackCommunities
Powered by
We continue to get `Timed out fetching a new conne...
# orm-help
j
We continue to get 
Timed out fetching a new connection from the connection pool. More info: <http://pris.ly/d/connection-pool> (Current connection pool timeout: 10, connection limit: 3)
on a project that has the connection string with the connection pool to 100. And we are verifying that when the app starts up. It is a nestjs app running on Azure connecting to an AWS Aurora database. We have another project that is almost identical that is not having this issue. They share the same prisma client library. We are trying to get this to production ready but have no idea why this continues to happen
what is weird is we only have this running on one app service instance, and only one user hitting it.
Copy code
{
clientVersion: 3.8.1, 
code: P2024, 
message: 

Invalid `prisma.login.findFirst()` invocation:


  Timed out fetching a new connection from the connection pool. More info: <http://pris.ly/d/connection-pool> (Current connection pool timeout: 10, connection limit: 3)
, 
meta: {
connection_limit: 3, 
timeout: 10
}, 
name: Error, 
stack: [Filtered]
}
n
Hey Jonathan 👋 I’ve forwarded your message to our Engineering team, will let you know when I hear back anything. In the meantime, would you mind sharing some more logs by enabling the 
DEBUG
env var and setting the 
log
option when instantiating 
PrismaClient
? 🙂
Also, the connection limit in your error seems to be set at 
3
while you mentioned it was set to 
100
. Could you maybe share an obfuscated version of your connection string as well?
j
Thanks I'm out for a bit but as soon as I get to my office I will get it to you
that is what our connection string looks like
56 Views
Open in Slack
PreviousNext
Powered by