Thanks Graham, I agree now that I understand it in more detail...

- Pieter



On 24 mei, 00:31, Graham Dumpleton <[email protected]> wrote:
> If you use embedded mode you could use:
>
> http://httpd.apache.org/docs/2.2/mod/mpm_common.html#listenbacklog
>
> to set listen backlog to zero. I still don't believe it is a good idea
> as you are likely going to reject a lot of requests.
>
> You could set it to some non zero small value, but still not sure how
> desirable it is. You can at least play with the idea I guess.
>
> Graham
>
> On 24 May 2011 09:21, Pieter Ennes <[email protected]> wrote:
>
>
>
>
>
>
>
> > Hello Graham,
>
> > I see your point.
>
> > We have a situation where we want the server to give back an error
> > straight away, so we can fail over to a different node entirely; when
> > the connection hangs for a long period of time, this mechanism fails.
> > But I could look into switching to embedded mode for this specific
> > application, would there be a solution there?
>
> > - Pieter
>
> > On May 23, 11:28 am, Graham Dumpleton <[email protected]>
> > wrote:
> >> To do it would mean having configuration options to set the listen
> >> back log for the UNIX listener socket that a daemon process group
> >> listens on, plus a configuration option to disable the back off and
> >> reconnect when connection failures occur when connecting to the daemon
> >> processes from the Apache child processes.
>
> >> Overall I cannot think of any good reason to do this though with the
> >> result possibly being less stable/predictable behaviour. It possibly
> >> would render useless the ability of daemon processes to be restarted
> >> by touching the WSGI file as you would cause 503 all the time when you
> >> do it.
>
> >> Can you now explain why you would want to do this?
>
> >> Graham
>
> >> On 23 May 2011 20:17, Pieter Ennes <[email protected]> wrote:
>
> >> > That would be daemon mode primarily...
>
> >> > - Pieter
>
> >> > On 23 mei, 11:06, Graham Dumpleton <[email protected]> wrote:
> >> >> Are you specifically talking about embedded mode or daemon mode?
>
> >> >> Graham
>
> >> >> On 23 May 2011 20:02, Pieter Ennes <[email protected]> wrote:
>
> >> >> > Hi all,
>
> >> >> > I'm looking for a way to have mod_wsgi return a 503 response straight
> >> >> > away whenever no process/thread is available, instead of having the
> >> >> > incoming requests queue up first. Is there any way to do this? Based
> >> >> > on the detailed description here:
>
> >> >> >  http://groups.google.com/group/modwsgi/browse_thread/thread/706cff32a...
>
> >> >> > I'm not sure if this is currently possible. Can I file a feature
> >> >> > request for this?
>
> >> >> > Thanks,
> >> >> > - Pieter
>
> >> >> > --
> >> >> > You received this message because you are subscribed to the Google 
> >> >> > Groups "modwsgi" 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 
> >> >> > athttp://groups.google.com/group/modwsgi?hl=en.
>
> >> > --
> >> > You received this message because you are subscribed to the Google 
> >> > Groups "modwsgi" 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 
> >> > athttp://groups.google.com/group/modwsgi?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "modwsgi" 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 
> > athttp://groups.google.com/group/modwsgi?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" 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/modwsgi?hl=en.

Reply via email to