> I've locked all the <cffile>s <cfexecute>s and <cfhttp>s which has been > on the server since Tuesday night.
So have things improved at all ?? > However, we've been seeing another, > possibly unrelated, problem caused by a slow LDAP server which we use > for authentication. > > 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. > >cause the server to restart I persume its the cfserver you are talking about :-) Actually I never heard about locking & cfldap tag. I must say in the one time I had to use cfldap (back in cf3 with a MS LDAP server 'oxymoron?'), I wasn't very impressed by it. Might be better to impliment your LDAP calls in Java (cfx or object with CreateObject) - should be easy(ish) using JNDI. > My plan was to write back to the list when we've 'tried everything' so > I'll keep you updated. > > Thanks again for your help with this, No worries. Hope to learn from your issues.. > Simon > > --- > [EMAIL PROTECTED] > Applications Development Manager > Warwick Business School > > >>> [EMAIL PROTECTED] 25/07/2002 11:29:11 >>> > Hi Simon, You get anyway with this? > > Justin > > > -----Original Message----- > > From: Simon Harper [mailto:[EMAIL PROTECTED]] > > Sent: Saturday, July 20, 2002 9:48 AM > > To: CF-Linux > > Subject: Re: Simons crashing server WAS RE: Client vs Session > variables > > > > > > HI Justin - thanks for writing back. > > > > --- > > [EMAIL PROTECTED] > > Applications Development Manager > > Warwick Business School > > >>> [EMAIL PROTECTED] 07/19/02 20:10 PM >>> > > > Just rereading your mails > > > > >> 1. All our session/application variables are locked >> for > writing, > > and using > > >> Auto read locking. > > > > > Can you clarify this? Are you using any cfexecutes / > cfx 's / > cffile > > without > > > locking? > > > > Erm, yes. We're using unlocked cfexecutes and cffiles all over the > > place. This is the first I've heard about locking those tags, so I > guess > > that might be it ?... > > > > > How many apps are you hosting? > > > > Difficult to determine when a web page stops and an application > starts, > > but if we're talking use of the cfapplication tag it's about 10. > > > > > Have you looked in your web server logs for the > > > times you have entries like > > > > > "Warning","1026","07/18/02","19:43:42",,"Restarted > > > ColdFusion Application Server." > > > > > Look for the URLS requested (and the corresponding > > > cfm templates) around "07/18/02","19:43:42" etc.. > > > You might find a particular template. > > > > To be honest we've found this too hard as our main app is such that > > virtually all requests are for index.cfm, and according to form and > > session data different tags are called. At the time of the crashes > we > > see only those requests in the web logs, which doesn't help much. > > > > Thanks again for the locking tip - I'll get going. > > > > Cheers, > > > > Simon > > > > > > ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.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.
