hello, recently under not yet clearly defined circumstances (it isn't load), we sometimes get into the situation of a non-reacting sql server with the thrown exception:
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. In the connection string we define the pool with min 4 and max 100 - by the dimensions of the website suffering from this condition, this should be sufficient. Seems to me, something opens connections, but does not release them - but I have no real good idea, on how to debug this (especially as this shows only on the production server, as usual), to find the evil doer. Anyone could give me some hints, on how to approach this? We are using nh 2.1 with the rhino.commons base application for session management. -- Jan -- You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en.
