We had an Oracle listener hang. This caused big problems in
ColdFusion. The "timeout" attribute just didn't seem to work. I posted
this here before and it was suggested that the timeout clock doesn't start
until the SQL is sent. Since the listener was hung, I'm not sure how far CF
went with the connection. In anycase, the unresponsive threads brought down
a handful of servers just because one datasource was inoperable.
Is there anyway to avoid this in the future? It seems like CFs
error correction (timeout in the CF admin) flew out the window. Can I get
more error correction by using ADO? Thanks :)
EC
.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
