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]

Reply via email to