> In my case, I was having problems when the number of concurrent requests > went above 20 or 25. (I forget the details. I've been using this patch > for around 3-4 months... modulo changes I made today.)
Do you think this is a manifestation of this problem: http://www.mono-project.com/Article:ThreadPool_Deadlocks If so, it would be interesting to find out who is the consumer of the other threads in the thread pool. I wonder if we should set this limit in the managed code. > The patch by default limits the number of concurrent requests passed to > mod-mono-server to 20. After that, it holds onto (by default) up to 20 > more, checking periodically until the initial 20 decreases or a timeout > (hard-coded at 10 seconds). The two 20's are configurable with > MonoMaxActiveRequests and MonoMaxWaitingRequests. > > This will only work on Apache2 since it relies on the shared memory > dashboards. > > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list