Since this morning, I have switched to CF5. I'm still getting the Error 111, but in the logs, it looks like it's being caused by a Signal 11 (seg fault). Is there a way that I can see what is generating the Sig11?
BTW, I now have "Single Threaded Sessions" turned on. thanks ttyl mark leonard "Error","9225","11/02/01","13:09:25",,"Unable to write reply -- client browser stopped waiting for request. " "Error","9225","11/02/01","13:09:25",,"Unable to write reply -- client browser stopped waiting for request. " "Fatal","7175","11/02/01","13:09:25",,"Caught a fatal signal (11) - Aborting" "Information","1024","11/02/01","13:09:35",,"The ColdFusion Application Server started." > -----Original Message----- > From: Frank Hilliard [mailto:[EMAIL PROTECTED]] > Sent: November 2, 2001 9:09 Early > To: CF-Linux > Subject: Re: Error 111 > > > I've found multiple CF restarts are caused by not locking session > variables, particularly if they're used in a CF mailer. You have to lock > both the writes and the reads. Hope this helps. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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.
