Sorry this reply took so long, I am in the middle of changing jobs.
Anyway,
WSGIApplicationGroup %{GLOBAL}
does not change the rough frequency with which I see the problems. I
only added that directive for the port 80 virtual host, while the 443
virtual host doesn't have it. Should I add it to
http://www.cherrypy.org/ticket/916#preview
Graham can you review this ticket please to see if its compatible with
mod_wsgi please
The patch defenatly works for me.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
2009/5/2 Tim Valenta tonightslasts...@gmail.com:
Hello all-- I have yet to get down and dirty with my apache installation, so
I'm not 100% sure of the issue yet. I have access to the server right now,
but I'm a work currently and can't really just dedicate time to having a
look until
Hello all-- I have yet to get down and dirty with my apache installation, so
I'm not 100% sure of the issue yet. I have access to the server right now,
but I'm a work currently and can't really just dedicate time to having a
look until probably tomorrow. I thought I'd pitch it out here though,
On May 1, 4:59 pm, gert gert.cuyk...@gmail.com wrote:
http://www.cherrypy.org/ticket/916#preview
Graham can you review this ticket please to see if its compatible with
mod_wsgi please
The patch defenatly works for me.
Somebody has been busy :)
gert hello :)
gert
Thanks-- I'll monitor that stuff in the near future.
I'm fairly certain that mod_python is not enabled or installed on the
server, though I will double-check that.
The 'apache restart' seemed to actual cure the problem, whereas the memory
creep seemed to happen over the day full of 'reload'
2009/5/2 gert gert.cuyk...@gmail.com:
http://www.cherrypy.org/ticket/916#preview
Graham can you review this ticket please to see if its compatible with
mod_wsgi please
The patch defenatly works for me.
Nothing to do with mod_wsgi. That is a CherryPy WSGI server issue with
its handling of
Noting that init script reload is equivalent to apachectl restart and
init script restart is equivalent to apachectl stop and start.
At least I think that is the case for Linux distributions. Confusing isn't it.
When I talk about it, I talk about what apachectl does, not the init script.
I have told you before that calling read() with no argument is
disallowed by WSGI specification. You are only allowed to at most read
CONTENT_LENGTH. Don't do that and you have problems with WSGI servers
that don't implement an input end sentinel.
Graham
2009/5/2 gert gert.cuyk...@gmail.com:
Doh, I forgot about that, anyway works now :)
On May 2, 12:33 am, Graham Dumpleton graham.dumple...@gmail.com
wrote:
I have told you before that calling read() with no argument is
disallowed by WSGI specification. You are only allowed to at most read
CONTENT_LENGTH. Don't do that and you have
10 matches
Mail list logo
