Hi Stefan,

On 28/12/2010, at 23:15, Stefan de Konink wrote:

> Using the following setup:
> 
> Cherokee (svn update afternoon)
> |
> v
> HTTP reverse proxy
> |
> v
> eJabberd (mod_http_bind)
> 
> (keepalive/chunked encoding all off)
> 
> I observe that after exactly 30s Cherokee throws a 504 Gateway Timeout.
> 
> Now somethings that I do know: ejabberd definately does respond to the 
> request I can just see that from the erlang logfile.
> 
> =INFO REPORT==== 2010-12-28 23:13:26 ===
> I(<0.464.0>:ejabberd_listener:232) : (#Port<0.14917>) Accepted connection 
> {{127,0,0,1},49119} -> {{127,0,0,1},5280}
> 
> =INFO REPORT==== 2010-12-28 23:13:26 ===
> I(<0.7403.0>:ejabberd_http:138) : started: {gen_tcp,#Port<0.14917>}
> 
> 
> So I could make a claim that something strange is going on, more interesting 
> the problem seems to occur (and is reproducable) to a POST, 30s after the 
> first page load.
> 
> Where to look for?

I don't think I have understood the problem well enough to be able to advise 
you, actually.

When you say "HTTP reverse proxy", do you mean Cherokee's or something else? 
Besides, I'm wondering why you turn off keep-alive and chunked-encoding; is 
there a reason?

Aside from that, I'd personally begin by enabling CHEROKEE_TRACE=all and 
checking what's going on (when and how the request arrives, how it's handled, 
and when and how the response is sent).

Cheers!

--
Octality
http://www.octality.com/

_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to