Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cherokee: dev

Issue 587 in cherokee: HTTP reverse proxy keepalive broken

 

 

Cherokee dev RSS feed   Index | Next | Previous | View Threaded


codesite-noreply at google

Sep 27, 2009, 7:12 AM

Post #1 of 5 (200 views)
Permalink
Issue 587 in cherokee: HTTP reverse proxy keepalive broken

Status: New
Owner: ----

New issue 587 by praseodym: HTTP reverse proxy keepalive broken
http://code.google.com/p/cherokee/issues/detail?id=587

It looks like the HTTP reverse proxy keepalive function is broken. I'm
running a comet-enabled
application within Jetty, proxied by Cherokee. With keepalive enabled,
connections are dropped
randomly causing the application to hang randomly. With keepalive disabled,
the problems
disappear and the application runs fine.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev


codesite-noreply at google

Sep 27, 2009, 7:16 AM

Post #2 of 5 (191 views)
Permalink
Issue 587 in cherokee: HTTP reverse proxy keepalive broken [In reply to]

Updates:
Labels: Type-Defect Priority-Medium OpSys-All Component-Logic Usability

Comment #1 on issue 587 by ste...@konink.de: HTTP reverse proxy keepalive
broken
http://code.google.com/p/cherokee/issues/detail?id=587

(No comment was entered for this change.)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev


codesite-noreply at google

Sep 29, 2009, 12:39 AM

Post #3 of 5 (183 views)
Permalink
Issue 587 in cherokee: HTTP reverse proxy keepalive broken [In reply to]

Comment #2 on issue 587 by alobbs: HTTP reverse proxy keepalive broken
http://code.google.com/p/cherokee/issues/detail?id=587

When you said you disabled keep-alive, did you mean on Cherokee?

I'm just guessing here, but.. did you try to increase the global keep-alive
limit
value in Cherokee? The browser-web server connection might be closed by the
server
when it detects a timeout (and the reverse proxy might have had nothing to
do with it).

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev


codesite-noreply at google

Sep 29, 2009, 12:52 AM

Post #4 of 5 (183 views)
Permalink
Issue 587 in cherokee: HTTP reverse proxy keepalive broken [In reply to]

Comment #3 on issue 587 by ste...@konink.de: HTTP reverse proxy keepalive
broken
http://code.google.com/p/cherokee/issues/detail?id=587

In this case ment the keep-alive connection to the backend server.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev


codesite-noreply at google

Sep 29, 2009, 4:20 AM

Post #5 of 5 (182 views)
Permalink
Issue 587 in cherokee: HTTP reverse proxy keepalive broken [In reply to]

Comment #4 on issue 587 by praseodym: HTTP reverse proxy keepalive broken
http://code.google.com/p/cherokee/issues/detail?id=587

I disabled the backend keepalive function; after this things started to
work normally. I'll check if increasing the
global limit helps (would actually be nice if there would be a separate
backend keepalive limit)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

Cherokee dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.