[Mono-list] Some issues with mono 2.0

Maxim makska at yandex.ru
Fri Sep 26 06:08:02 EDT 2008


Hmm, it seems like we solved problem just partially.

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.

Is option "MonoMaxWaitingRequest" implemented?
Is the only way to solve this situation in upgrading server CPU?

Best wishes,
Max Karavaev

> Hello!
> It seems like we solved this problem.
> Joshua is right.
> Settings
> MonoMaxActiveRequests 10
> MonoMaxWaitingRequests 100
> fixed exponentially grow of connections by reducing concurrent processes.
> On other server with two dual core xeons this problem never appear, but
> for other with single core duo 2 these settings are very important.
> And settings
> MonoAutoRestartMode Requests
> MonoAutoRestartRequests 10000
> reduce memory consumption by restarting hight loaded websites.
> May be with compacting GC this option become obsolete. I've never seen
> such a situation on IIS+.Net.
> It would be great to write some tips about these situations on mod_mono
> FAQ page.
> Thanks a lot for help!
> All the best,
> Max Karavaev
>> Hello Maxim,
>>     We are unaware of this problem, do you think you could provide a
>> test case that illustrates this problem so we can look into it?
> _______________________________________________
> Mono-list maillist  -  Mono-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list

More information about the Mono-list mailing list