This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi Mindscape, do you have any troubleshooting tips for tracing the cause of this error? "Pooling=True" is set in the connection string, which seems to be useful for improving the responsiveness of multiple concurrent queries. Cheers, Donovan. Event Type: Warning For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. |
|
|
Hi :) This is coming from the underlying provider - which provider are you using for this? (assumption would be SQL Server). It also looks like you have impersonation on, so the connections will be held on a per user basis - so if you have as many active connections as you have users authenticated you would be running out of pool connections fairly quickly. Have you looked at playing with the number of connections in the pool? Lastly - are you using the PerRequestScope for your UnitOfWork?
Cheers, Jeremy |
|