[Zope] Erratic HTTP 500

[Dieter Maurer]

sean.upton@uniontrib.com writes:
 > Anybody have any thoughts on what problems might trigger an HTTP 500 in
 > Zope?
Provided that the 500 response is generated by Zope and not
the SQUID in front, it means that there has been an exception
that ZPublisher is unable to map to a different response
code (such as 'Unauthorized' and 'redirect').

Catch exceptions in your process and print them.
Then you get a better feeling what goes wrong.

If the response is generated by SQUID, then Zope died (or timed out).
In this case, use the "-M" option (-> mailing list archives),
to analyse the circumstances of the deaths.


Dieter