Hello, does anyone know what could cause this issu...
# orm-helpd
Daniell
10/26/2021, 7:46 AMHello, does anyone know what could cause this issue? I have a server side rendered page in Next.js and a standalone Node.js server which only creates an instance of PrismaClient once (I am not using Next.js's server), I get this error right away when I visit the home page and Next.js makes a call to the standalone API
Copy code
Timed out fetching a new connection from the connection pool. (More info: <http://pris.ly/d/connection-pool>, Current connection limit: 3)r
Ryan
10/26/2021, 7:51 AM@Daniell 👋
I would suggest restarting your database to clear all connections and then setting up Prisma in the following manner so that new connections are not made.
d
Daniell
10/26/2021, 7:53 AMThanks I can try restarting the database, but I am not using Prisma in Next.js, I have a standalone server with a connection that's only made once in the entrypoint file
r
Ryan
10/26/2021, 8:44 AMAre you using some kind of hot reloading? That could also cause issues.
d
Daniell
10/26/2021, 8:46 AMI double checked but it's not the case, it happens in our master branch of Vercel
r
Ryan
10/26/2021, 11:41 AMIs it happening on development or production?
d
Daniell
10/26/2021, 11:53 AMIt happens in production
Daniell
10/26/2021, 11:55 AMThe url is next.foodsy.eu if you're interested in checking the network requests, the error shows right away, yet in the backend there is only 1 prisma client initialisation
r
Ryan
10/26/2021, 12:02 PMWhere’s your backend hosted?
d
Daniell
10/26/2021, 12:04 PMIt's hosted on AWS using EC2 blue/green deployment
r
Ryan
10/26/2021, 12:06 PMCould you restart the database and increase the connection limit to around 5-8?
Ryan
10/26/2021, 12:07 PMAlso possibly run
prisma.$disconnect()d
Daniell
10/26/2021, 12:11 PMI will try
👍 1
Daniell
10/26/2021, 12:25 PMNo success 😅 Added
Copy code
process.on("SIGTERM", async () => {
await prisma.$disconnect()
})?connection_limit=5👍 1
Daniell
10/26/2021, 2:17 PMThanks it's fixed now!
🙌 1
3 Views