Great Dave....thanks for the error handling advice...I'lll take a peak.

You seem to say that I can't use nested CFTRY tags (my index template file is currently wrapped in  a CFTRY).  Is that the case?  I currently use CFTRY in some files that get included in the template with no problems.

Bryan Stevenson B.Comm.
VP & Director of E-Commerce Development
Electric Edge Systems Group Inc.
t. 250.920.8830
e. [EMAIL PROTECTED]

---------------------------------------------------------
Macromedia Associate Partner
www.macromedia.com
---------------------------------------------------------
Vancouver Island ColdFusion Users Group
Founder & Director
www.cfug-vancouverisland.com
  ----- Original Message -----
  From: Dave Watts
  To: CF-Talk
  Sent: Tuesday, December 09, 2003 9:20 AM
  Subject: RE: Strange error CFMX 6.1

  > I'm getting a really harsh result from a seemingly basic CF error.  
  > It seems to be happening only when using CFINVOKE or within a function
  > in a CFC. The cause is simple things like say leaving the closing
  > double quotes off the returnvariable attribute value (like this
  > returnvariable="MyReturnVar).
  >
  > This causes a CF error on the screen which doesn't even get caught
  > (whole page is wrapped in a CFTRY with a CFCATCH that dumps the error
  > to the page) and grinds the server to a halt (we're talkin Windows
  > draggin it's arse big time).  Whatever is going on it doesn't seem to
  > play by the rule set in CF Admin to timeout long running requests after
  > 30 seconds!!!
  >
  > Any ideas?  I just can't see why such a simple error would kill the
  > server....so far reboots are the only solution.

  I'm not sure why this would kill the server either. However, I'm not
  surprised that this isn't being caught with CFTRY/CFCATCH, since it's not a
  runtime exception, but rather a parsing error. You should be able to catch
  it with CFERROR TYPE="REQUEST" or the site-wide error handler, though. On
  the other hand, if this is killing the server, it may not respect your error
  handlers, either.

  Also, I would recommend that, instead of wrapping your entire page within a
  CFTRY, you should use the CFERROR TYPE="EXCEPTION" tag. This allows you to
  reserve CFTRY for cases where you have a specific problem that you expect,
  and a specific solution for that problem.

  Dave Watts, CTO, Fig Leaf Software
  http://www.figleaf.com/
  phone: 202-797-5496
  fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to