Thanks again for the reply Dave. Replies below:

> You should certainly be as specific as possible within your exception
> handler. 

Let me be a bit more specific. In terms of a CF timeout, do you (or 
anyone reading) happen to know what exception code CF spits out? The 
types listed for CFCatch are:

Application
Database
Template
Security
Object
missingInclude
Expression
Lock
Custom_type
Any (default)

There's also a host of Advanced Exception types which I won't list here 
since its a long list.

I'm currently using "Any" for my CFCatch but I would like to narrow that 
down so I can explicityly trap for the timeout.

> That said, your exception handler should trap and dispatch your
> exception before the CFERROR tag anyway. If it's not doing that, you
> probably have a logical error in your exception handling code.

To clarify, my page level error handling (CFTRY, CFCATCH, et al) is 
firing before the site wide error handler. I should've mentioned that 
before.

What I would like is to completely prevent the default site wide error 
handler from kicking in as well during a ColdFusion timeout exception.

So to summarize:

If a *timeout* occurs on this *specific* .cfm page, then bypass the 
site-wide error handler completely and only use the CFTRY/CFCATCH code I 
have in place.

In any other circumstance use the site-wide error handler.

Rey...



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
ColdFusion MX7 and Flex 2 
Build sales & marketing dashboard RIA’s for your business. Upgrade now
http://www.adobe.com/products/coldfusion/flex2

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:270241
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to