Build breaking over two queries
Answered
Great Spotted Woodpecker posted this in #help-forum
Great Spotted WoodpeckerOP
I started a project to try the new Next.js (15) version with Typescript.
It's a simple loan system for a fictional library with CRUDs for:
- Books
- Book types
- Customers
- Genres
- Loans
- Users
I was able to do everything, but after I created the create loan page (the last thing I was working on) the production build started breaking.
I followed the same pattern I used on the other cruds, so I'm really lost.
In dev it works fine and I'm using the same production db for development (postgres), so is the same credentials in dev and prod as it's a test project.
If I comment the queries I need for the selects and use a static array with the same data, it builds just fine.
I could't find anything related to this in the issues on github and upgrading the project to canary didn't fix it.
- The project: https://github.com/larissathasdefar/nextjs-library
- The crud root: https://github.com/larissathasdefar/nextjs-library/blob/main/app/admin/loans/create/page.tsx
- The build error message:
PS: Mind that the folder error (ex: /seed/route) changes in every build, so it's not that. This started only after I added the admin/loans/create files with the queries.
This is driving me mad!!!!!
It's a simple loan system for a fictional library with CRUDs for:
- Books
- Book types
- Customers
- Genres
- Loans
- Users
I was able to do everything, but after I created the create loan page (the last thing I was working on) the production build started breaking.
I followed the same pattern I used on the other cruds, so I'm really lost.
In dev it works fine and I'm using the same production db for development (postgres), so is the same credentials in dev and prod as it's a test project.
If I comment the queries I need for the selects and use a static array with the same data, it builds just fine.
I could't find anything related to this in the issues on github and upgrading the project to canary didn't fix it.
- The project: https://github.com/larissathasdefar/nextjs-library
- The crud root: https://github.com/larissathasdefar/nextjs-library/blob/main/app/admin/loans/create/page.tsx
- The build error message:
Failed to build /admin/book-types/page: /admin/book-types (attempt 1 of 3) because it took more than 60 seconds. Retrying again shortly.
Failed to build /seed/route: /seed (attempt 1 of 3) because it took more than 60 seconds. Retrying again shortly.
PS: Mind that the folder error (ex: /seed/route) changes in every build, so it's not that. This started only after I added the admin/loans/create files with the queries.
This is driving me mad!!!!!
Answered by itsfinniii
I don't know if you also have to call
await db.close() or something similar. If you do, then you might create a bunch of connections and then they get limited, and you cannot connect anymore, the timeout of 60 seconds get reached and an error is created18 Replies
Are the CLI logs from the build on production or on development?
Considering the connection failed, see if the database is still online, if the environment variables are correct and (attempt to) connect to the correct database, as the code itself seems fine (at a quick look)
Great Spotted WoodpeckerOP
The CLI are from development, but on vercel it looks the same as well.
The database is on, I already tried updating .env in case the keys changed, but the problem persists.
The database is on, I already tried updating .env in case the keys changed, but the problem persists.
If I remove the promise for 2 arrays it builds, if I use the queries, it dont
In development it run alright, so is not the query itself as well
In development it run alright, so is not the query itself as well
Can you confirm one of the two queries acually work? A simple console.log on the rows that the database returns is already enough, because that way. If you cannot do it that way, maybe try putting the queries in pgAdmin (or any tool you use to execute SQL on your Postgres DB).
It probably is something on the database side, considering it reaches a 60 second timeout... maybe the database reached a connection limit?
The queries by themselves look fine...
Great Spotted WoodpeckerOP
this is when I do the console.log and run build
it log its results
it log its results
in development it runs fine
I assume Prod and Dev has different databases?
Great Spotted WoodpeckerOP
but now you said something that is making me wondering if the free plan of vercel has limitations for the database
I'm going to look about that
I'm going to look about that
its the same database because is a test project
I don't know if you also have to call
await db.close() or something similar. If you do, then you might create a bunch of connections and then they get limited, and you cannot connect anymore, the timeout of 60 seconds get reached and an error is createdAnswer
Great Spotted WoodpeckerOP
oh, it seems I never called a
let me try adding this!
db.close() on my codelet me try adding this!
I have no clue if you need to do it though... maybe it helps, maybe it won't.
Great Spotted WoodpeckerOP
THANK YOUU VERY MUCH!!
it's related to the amount of connections to the database
if I remove another crud with its query files IT BUILDS!!
now I can take a look to how I can fix that, thank you!!
it's related to the amount of connections to the database
if I remove another crud with its query files IT BUILDS!!
now I can take a look to how I can fix that, thank you!!
Great, hope to have been of help. Good luck!
Great Spotted WoodpeckerOP
Some related resource in case anyone needs in the future:
https://www.reddit.com/r/nextjs/comments/12yhgis/how_to_have_a_single_permanent_database/
https://vercel.com/guides/connection-pooling-with-serverless-functions
https://supabase.com/blog/supabase-pgbouncer
For now I fixed using
https://www.reddit.com/r/nextjs/comments/12yhgis/how_to_have_a_single_permanent_database/
https://vercel.com/guides/connection-pooling-with-serverless-functions
https://supabase.com/blog/supabase-pgbouncer
For now I fixed using
await client.release(); after my queries