This can happen if you use debug=True in your application and you have loaded several API pages or endpoints that have fallen out of the system.
The reason is that starting the debug version of the application allows you to disable the live debugger on the error page. This live debugger supports all resources from request processing so that you can examine them. This means that the database connection cannot be reworked.
You should not use debugging mode for the production version of your application (except for problems like this, this is a security risk), and the debugger will often not work in any case (it is designed to work with the test server of flacks, and not with machine guns). Therefore, in prod, the solution is to disable debugging.
If you have this problem in dev using debug mode - this is a limitation. You should not hit the dev server so hard, or you can increase the limit. Keep in mind that 15 connections are usually enough to serve a large number of concurrent requests when they are correctly processed. It is only in debugging that they tend to end up.
source share