that's a bummer. You might try making a CherryPy filter that logs at
the different points in the request cycle so that you can get an idea
of where it's getting locked up.
"""Base class for CherryPy filters."""
class BaseFilter(object):
"""
Base class for filters. Derive new filter classes from this, then
override some of the methods to add some side-effects.
"""
def on_start_resource(self):
"""Called before any request processing has been done"""
pass
def before_request_body(self):
"""Called after the request header has been read/parsed"""
pass
def before_main(self):
""" Called after the request body has been read/parsed"""
pass
def before_finalize(self):
"""Called before final output processing"""
pass
def before_error_response(self):
"""Called before _cp_on_error and/or finalizing output"""
pass
def after_error_response(self):
"""Called after _cp_on_error and finalize"""
pass
def on_end_resource(self):
"""Called after finalizing the output (status, header, and
body)"""
pass
def on_end_request(self):
"""Called when the server closes the request."""
pass
On Jun 15, 2006, at 11:12 AM, mulicheng wrote:
>
> I'm running a couple instances of my application in production and
> balancing them with lighttpd's mod_proxy. (Thanks all for getting me
> on the right track with that.)
>
> On a pretty regular frequency, one of the instances will stop
> responding to requests. (The site stays up because there is more than
> one instance running.)
>
> Does anybody have any suggestions on how to debug the process that is
> still running? I'm not sure if it is something in my business logic
> causing the problem or if there is something wrong with TG/Cherrypy.
> The process is still listening on the port I started it on, a tcp
> connection can be made, but no response is delivered and there is no
> debugging information printed.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" 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/turbogears
-~----------~----~----~----~------~----~------~--~---
