Dear Users,
Often at times when the code encounters an exception, mongrel starts
throwing error 500 (after which most other cluster instances are
affected).
My queries are
- why does an exception in one thread have to affect others?
- how can I stop mongrel throwing 500 and start showing me the actual
error on the browser (this will make things so much more easier)
- Can anyone direct me to some detailed documents on mongrel
configuration?
regards
Mohammed. A
On 3/13/08, [email protected] [email protected] wrote:
Dear Users,
Often at times when the code encounters an exception, mongrel starts
throwing error 500 (after which most other cluster instances are affected).
My queries are
- why does an exception in one thread have to affect others?
I think you need to give us a bit more detail. Like, are you talking
about
actual threads within one process, or different processes, which the
word
“cluster” above hints? And are you using a framework like Rails or
Merb, or
are you building your own registered handlers in Mongrel?
Best regards,
/David