You define the pool size in either app.cfg or prod.cfg. Your's is obviously configured at size 10 with an overflow of another 10.
Depending on your setup and particularly hardware, you may want to increase those values. It's basically the number of database connections your server can utilize at any one point. In your case, if the query you use takes a bit to process, that one connection is unusable until the query finishes. If there are enough requests coming in and queries take a bit to process, you end up blocking all available connections (10), so the server starts using the "overflow" setting - another 10. Once those are exhausted, which makes it a total of 20 currently used database connections, you get this error. So what you'd need to do is to increase the number of connections your database accepts to match or exceed the combined total of the pool size plus the overflow. I'm running a website which currently has a pool setting of 80 with overflow 40 on 2 server processes (making it a total of 2x80 + 2x40 = 240 maximum database connections). However, I do have the hardware to support that (quad processor 4GB memory) > TimeoutError: QueuePool limit of size 10 overflow 10 reached, > connection timed > out, timeout 30 > > This error is happening when a number of requests are coming. > KIndly please tell me why this causing? -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
