RE: Solved: division by 0 error

2006-12-01 Thread Dave Watts
> It's interesting that this issue has not come up until we > deployed multiple instances. My guess is that it's the session replication of an empty session object that's causing the problem. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest calib

RE: Solved: division by 0 error

2006-12-01 Thread Russ
d multiple instances. Russ > -Original Message- > From: Andy Matthews [mailto:[EMAIL PROTECTED] > Sent: Friday, December 01, 2006 3:13 PM > To: CF-Talk > Subject: RE: Solved: division by 0 error > > If you clear SESSION itself you're asking for trouble. > > Try

RE: Solved: division by 0 error

2006-12-01 Thread Russ
#2 would be nice... I think the technote explains how to do structclear without killing the session... Russ > -Original Message- > From: Dave Watts [mailto:[EMAIL PROTECTED] > Sent: Friday, December 01, 2006 2:55 PM > To: CF-Talk > Subject: RE: Solved: division by 0 err

RE: Solved: division by 0 error

2006-12-01 Thread Andy Matthews
EMAIL PROTECTED] Sent: Friday, December 01, 2006 1:42 PM To: CF-Talk Subject: RE: Solved: division by 0 error I think I got it. On logout, we were using structClear(session), and while working on a workaround, I coincidentally came to the livedocs for structClear, which mention never to use it on se

RE: Solved: division by 0 error

2006-12-01 Thread Dave Watts
> So my question is what is the correct way to kill a session? If you simply want to disconnect the session from the user's browser, just delete the session cookie and let the session itself expire normally. If you're concerned about memory usage, you could delete everything from the session that'

RE: Solved: division by 0 error

2006-12-01 Thread Russ
I think I got it. On logout, we were using structClear(session), and while working on a workaround, I coincidentally came to the livedocs for structClear, which mention never to use it on session. There is a technote that explains that it deletes the cfid/cftoken/jsessionid and that's bad... ht