I have seen this white screen of death before too on production servers. The problem I found was that MySQL was dropping the client connection and Jifty does not on each request perform ping-and-reconnect yet. I haven't hacked it in because I wasn't sure what the best place to do it in the core would be.
<br><br>However, the work around is very simple. At the very top of your dispatcher add:<br><br>before '**' => run { Jifty->handle->connect };<br><br>That will not reconnect if the current connection is still up and running, but it will ping the database connection to check for liveness. If it fails the liveness test, it will reconnect.
<br><br>That's resolved the problem on my servers. I hope that helps.<br><br>Cheers,<br>Andrew<br><br><div><span class="gmail_quote">On 1/16/08, <b class="gmail_sendername">Stanislav Sinyagin</b> <<a href="mailto:ssinyagin@yahoo.com">
ssinyagin@yahoo.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I've let my application run in native jifty server running overnight, and
<br>in the morning all web output was empty:<br><br>the server responded, and it rendered everything from my mason templates,<br>but it looked like the database was completely empty. After restarting<br>jifty server it worked fine again.
<br><br>That time I started it with >/dev/null, with optimistic thought<br>that I wouldn't need it :-)<br><br><br><br><br><br><br>_______________________________________________<br>jifty-devel mailing list<br><a href="mailto:jifty-devel@lists.jifty.org">
jifty-devel@lists.jifty.org</a><br><a href="http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel">http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel</a><br></blockquote></div><br>