[Mono-list] Some issues with mono 2.0

[Maxim]

Joshua Tauberer wrote:
> Maxim wrote:
>> Hmm, it seems like we solved problem just partially.
>> With
>>
>> MonoMaxActiveRequests 10
>> MonoMaxWaitingRequests 100
>>
>> settings there are a lot messages like "Maximum number (10) of
>> concurrent mod_mono requests to
>> /tmp/mod_mono_dashboard_nike-outdoor.ru_2.lock reached. Droping
>> request."
>> and some visitors get "Service Temporary Unavailable" error.
>
> Well that's exactly what's going to happen when you limit the number
> of connections --- the hope is that with a reasonably large
> MonoMaxWaitingRequests it doesn't happen often.
So, we should to increase MonoMaxWaitingRequests ?   "Service Temporary
Unavailable" error appears when amount of waiting requests reach limit
or when waiting requests reach apache timeout?

>> Is option "MonoMaxWaitingRequest" implemented?
>
> Yes. (I did it myself...)
Great respect!
> If you access a page during high load and see your browser waiting
> with no response for a while, that's MonoMaxWaitingRequest in action
> holding onto the request until it gets a chance to be processed.
Yes, exactly. But sometimes after waiting browser get response "Service
Temporary Unavailable".


Thanks again for your help!

All the best,
Max Karavaev