Jeff,
well, session variables at 1200 minutes is very, very long. There are very
good reasons to have timeouts shorter, so that memory can be collected. It
also depends on the items that are stored in the session objects. I've seen
instances where developers were storing large datatables in the session
store for each and every user, eating up absolutely tons of memory.
From what I understand, using a database when doing a clustered web site is
much better becuase a clustered web application can't of course share
session variables between nodes on the cluster.
Have you run some tests to see what how big the objects are getting to be in
the session store for each user? Also make sure you're doing some garbage
collection whenever you can. Even though .Net is managed code, one we still
need to ensure we are disposing of objects and resources as soon as we don't
need them to help speed up garbage collection.
--
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression
"WinDev" <Wi****@discussions.microsoft.comwrote in message
news:D6**********************************@microsof t.com...
>I have a weird one. My users will be on the system and suddenly get logged
out. I have forms authentication turned on with a 1200 minute logout (I
raised it that high to test this out.) Session timeout is also 1200
minutes.
It's almost acting as if its happening when IIS is cycling memory because
it
get's to be to much memory. (I've been working with Microsoft on this
problem
and they essentially say that have the system chew up memory is normal and
OK. Just cycle memory.)
The system is on a cluster - I don't know if that would cause a problem.
I'm
thinking of changing the memory from inproc to DB but don't know if that
will
help any.
Any thoughts?
Jeff.