Everything like this needs to be tested but I don't see it causing a
negative impact if your servers are already getting hammered.
How many sessions are you talking about, are you monitoring these with JRun
metrics?
I have seen session run-ups from HTTP probes, since they do not send in
cookies, and they run every x seconds. You might be seeing something
similar.
Mike
http://livedocs.macromedia.com/jrun/4/descriptordocs/jrun-web/jrun-web.htm
<http://livedocs.macromedia.com/jrun/4/descriptordocs/jrun-web/jrun-web.htm>
-----Original Message-----
From: Chris Boyce [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 22, 2004 10:37 AM
To: JRun-Talk
Subject: Sessions filling up memory
During peak hours, we have a lot of sessions resident in memory, and
occasionally JRun grinds to a halt with failed garbage collection.
Is it possible to use session elements like session-swapping,
session-swap-interval, and session-max-resident without having to use
persistence?
If so, is there a big performance hit in JRun when swapping excess
sessions to disk?
thanks
--
Chris Boyce
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
