On 17/04/2010, at 09:52, kevin beckford wrote:

> But I getting (in browser):
> 
> Unhandled Exception
> 
> Have you tried running those commands directly in your terminal, and 
> monitoring stderr?  I find that's a good way to get information that can 
> otherwise get swallowed.
> 
> I'm also getting the same Unhandled Exception error, using django. Cherokee 
> seems pretty flaky when using django, I've noticed.

That'd be kind of saying that the kernel is flaky because you got a 
Django/Python exception. It could be any of the other few layers of code 
involved. It might be Cherokee, indeed, although it could also caused by your 
application code, Django, flup, etc.

> What steps can be taken to make it run production ready? 

We'd need enough data to reproduce the problem: a complete backtrace, and a 
small example of how to get it to fail would be perfect. In case it were caused 
by a bug in Cherokee, that'd help us to get it fixed.

Cheers!

--
Octality
http://www.octality.com/

_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to