Actually, you're probably NOT seeing an error from SIG11s Sig11s are generic errors 
which generally don't bring CF down.

The error is going to lie someplace else in the system

Jesse Noller
[EMAIL PROTECTED]
Macromedia Server Development
Unix/Linux "special guy" 

> -----Original Message-----
> From: Simon Harper [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 10, 2002 4:08 AM
> To: CF-Linux
> Subject: Client vs Session variables
> 
> I've been trying to track down a 'SIG11' error that's bringing our site
> down every half an hour (on a good day).  I'm really not getting anywhere
> so I thought I might try a different approach ...
> 
> The users' experience is that when CF crashes their session is lost.  Our
> site uses session variables heavily for navigation.  We allow people to
> post messages to a dicussion board in one area of the site, so when they
> post their carefully crafted message they'll often find that their session
> is already toast and that the app has no idea what to do with their
> message (so throws it away).
> 
> On the other hand, the crashes per se are not that disruptive (if you're
> unlucky to see the error message you can usually 'refresh' to get going
> again).
> 
> So my question is, can we convert all our session variable into client
> variable which will be nicely maintained in the database, and should
> survive a restart ?
> 
> Thanks for any advice you may have,
> 
> Cheers,
> 
> Simon.
> 
> 
> ---
> [EMAIL PROTECTED]
> Applications Development Manager
> Warwick Business School
> 
> 
______________________________________________________________________
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