Hi! My bet would be that you have too few apache workers enabled. I cannot think of anything else without looking at the code (maybe some lock inside?)
I have tested mod_mono with up to 20 concurrent reuqest to the same resource (a httpHandler) and it worked without problems. Cheers! Michał Ziemski Adriaan napisał(a): > ok, thank you for you answer. > > After a while, the processes are stopped, but one, the main process. Now, > when i start a request to the server, which takes a lot of server time. Now, > from another browser, try to start the same website. The website is waiting > until the first request is ready, so, it seems not multithreaded. > > How can i solve this? > > thank you in advance > > Adriaan > > > > Michał Ziemski wrote: > >> Adriaan napisał(a): >> >>> I have configured apache2 with mod_mono. When i start apache, i see 5 >>> processes mod-mono-server2 started, but all but one are died after a >>> moment. >>> Thats logic because the same lock file is used: >>> /opt/mono-1.2.3/bin/mono >>> /opt/mono-1.2.3/lib/mono/2.0/mod-mono-server2.exe >>> --filename /tmp/mod_mono_server_default >>> >>> When i now start a httprequest which takes very long time, all other >>> clients >>> are still waiting for that process to stop. So, it seems, mod_mono is not >>> multithreaded. >>> How can i configure mod_mono to run multithreaded? >>> >>> thanx in advance >>> >>> >> Hi! >> >> It takes a while to process the initial request, because mod_mono is >> reading/parsing confgiuration files and compiling the page you >> requested. The following requests would be processed immediately. >> >> Cheers! >> Michał Ziemski >> >> _______________________________________________ >> Mono-list maillist - [email protected] >> http://lists.ximian.com/mailman/listinfo/mono-list >> >> >> > > _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
