On May 13, 2:35 pm, Deron Meranda <[email protected]> wrote: > The shutdown() is called with SHUT_WR (1), which means that > there is a socket half-close situation. This prevents additional > data from being sent by Apache to the wsgi process. However > it has no effect on the reading of data in the other direction. > > Generally the shutdown acts like an end-of-file marker, > it shouldn't affect the delivery of packets or their timing. > A pattern of using half-closes is not unusual and shouldn't > cause any unexplained delays; though it may require somebody > with more modwsgi internals knowledge to answer definitively. > > Aside from the unexplained 11 second delay, are your requests > otherwise working okay; or are they failing in some manner?
Thanks for the response. No, everything's working correctly, it's just the delay that's the problem (I've just observed a delay of nearly 90 seconds). I'd estimate that about 1 out of 50 requests are seeing a noticeable delay (> 2 secs); everything else is effectively instantaneous. Mark. -- 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.
