"Max client connections reached" on Transaction Pooler
Problem
How I Got Here
I am trying to connect a backend service to Supabase's database. Originally I was not having issues, but then it started reaching the maximum client connections on Supabase and therefore losing connection (?) and crashing. The service needs a constant connection to the database to continue running so it is easy to tell when something has gone wrong as the whole service stops. Around the time it started having issues, nothing was changed with the database settings nor the service code. It has been like this for around a day so far, after being fine for a couple weeks at least.What Does Not Work (Worked Previously)
- Connecting to Supabase database transaction pooler via Java service- Connecting to Supabase database transaction pooler via command prompt (
psql postgresql://postgres.xxxxxxxxxxxxx:xxxxxxxxxxxxxxxx@aws-1-us-east-2.pooler.supabase.com:6543/postgresWhat Does Work
- Connecting to Supabase auth- "Table Editor", "SQL Editor" via browser
- Connecting to Supabase database session pooler via command prompt
Environment
- Supabase: Nano, us-east-2, default if not higher pool size- Service: Java + Spring Boot + JDBC, server is IPv4 only
- Environment variables below (no other database-related environment variables):
- CLI psql: v16.3
Additional Notes
- Dashboard "Reports/Database" indicates that before and during the issue, database connections did not exceed 10 total at any timeAttempted Solutions (That Failed)
- Suspend service for extended time (1h) and retry connection- Restart Supabase project and immediately try connecting
- Restart Supabase service and wait a while doing nothing with it, then try connecting
- Change service environment variables to reduce number of attempted connections and decrease timeout times
- Add
SPRING_DATASOURCE_HIKARI_LEAK_DETECTION_THRESHOLD- Use session pooler instead of transaction pooler for service; this works for a few minutes (e.g. 30 mins) before stopping the service due to a different error:
o.h.engine.jdbc.spi.SqlExceptionHelper : HikariPool-1 - Connection is not available, request timed out after 30001ms
