I have a Fusebox site on two load-balanced Web servers that are using Client
variables stored in a central database to manage session information. The
database server is Sybase Adaptive Server Anywhere 6.0 and at this time
there is no redundancy on this database server. (I know...this is bad...we
are working on it.)
Currently when the database server goes down, the CFAPPLICATION tag with the
setting clientmanagement="yes" fails and that stops the entire site.
My idea is to CFTRY the CFAPPLICATION tag in app_globals.cfm and CFCATCH any
ODBC error. If an ODBC error is caught, I'd like to re-issue the
CFAPPLICATION tag with the setting clientmanagement="yes" changed to
clientmanagement="no". I'd also like to set an application variable called
ODBC_Available to False so I can let the user know that the database
functions are not available on the pages where the database is required.
This way, if the database server goes down, the Web site allows the user to
view pages that do not require the database.
Has anyone else built a work around for the CFAPPLICATION tag when dealing
with a temperamental database? For next year we are budgeting a redundant
database server configuration, so that should help in the long run.
Thanks,
Scott
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
