Connection Pool – One Process – Many Threads
My understanding of the connection pool is; if the connectionstring is the exact same, then we reuse the connection instead of make a new connection. My problem is that I’m creat
Solution 1:
It's doing exactly what you asked it to do. It's using connections from the pool but you've given it too much work. If you have 500 threads and 200 connections each thread can't have a connection. You should probably have as many connections as threads.
If you have yet more work to do (all 500 threads are busy), then you have to either return an error to the consumer or otherwise throttle the input into your application.
Post a Comment for "Connection Pool – One Process – Many Threads"