[Catalyst] Graceful handling of database failure

Oleg Pronin syber.rus at gmail.com
Fri Jun 20 19:25:13 BST 2008

I use it for 3 years. It might be used in production i think.
About 5 minutes: there are a set of attributes (ReconnectRetries,
ReconnectTimeout, etc) - you can manipulate how long it will reconnect.

2008/6/20 Mitch Jackson <perimus at gmail.com>:

> > You can use DBIx::Class with DBIx::RetryOverDisconnects as DBI handle a=
> > you will never got db server away message (it will reconnect as long as
> > required until database is up and no queries and transactions will be
> lost).
> Looks cool, but it's got a big warning on it saying it's not stable
> for production.  Also, if the database server goes away for 5 minutes,
> then instead of error 500 pages, now the website is just timing out to
> the browser. That's less descriptive for the end user, when what I'm
> aiming at is giving more of a "we've got a handle on things"
> appearance to the errors when they happen.
> /Mitch
> _______________________________________________
> List: Catalyst at lists.scsys.co.uk
> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
> Searchable archive:
> http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
> Dev site: http://dev.catalyst.perl.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20080620/7a6db=

More information about the Catalyst mailing list