Hi Bill,

I've been reading some of your messages from earlier in the year hoping
that they might shed some light on our problem.  The only thing is that
I couldn't find anywhere that you solved your problem and what it was.

Of course I hope I'm right in thinking that you *have* solved your
problem ...

Cheers,

Simon

---
[EMAIL PROTECTED]
Applications Development Manager
Warwick Business School

>>> [EMAIL PROTECTED] 25/07/2002 14:41:03 >>>
we were having our crashes without using cfldap at all

Bill Wheatley
Senior Database Developer
Macromedia Certified Advanced Coldfusion Developer
EDIETS.COM
954.360.9022 X159
ICQ 417645
----- Original Message -----
From: "Brian Panulla" <[EMAIL PROTECTED]>
To: "CF-Linux" <[EMAIL PROTECTED]>
Sent: Thursday, July 25, 2002 9:38 AM
Subject: RE: Simons crashing server WAS RE: Client vs Session
variables


> At 11:54 AM 7/25/2002 +0100, you wrote:
> >It's apparent that the <cfldap> tag will cause the server to
restart
> >when it doesn't like the response it gets.  We've noticed that if
you
> >set the timeout value it simply doesn't timeout, so we're writing a
> >command line LDAP client to do the authenication for us.
>
> Are you trapping for errors with CFTRY/CFCATCH? You should be
prepared to
> handle errors with these tags whenever you access a remote resource
(LDAP,
> SMTP, POP, etc) that may or may not be there.
>
>
> Brian
>
>
> _____
> Brian Panulla                           [EMAIL PROTECTED] 
> Chief Information Officer               814.238.6680
> Elmwood Media Group                     www.elmwoodmedia.com 
>
> 

______________________________________________________________________
Your ad could be here. Monies from ads go to support these lists and provide more 
resources for the community. http://www.fusionauthority.com/ads.cfm
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-linux%40houseoffusion.com/
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_linux or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to