Rick Reumann wrote:
"Hi my name is Rick and I use the Session to store objects."
"Hi Rick!"
<SUA - Session Users Anonymous - meeting/>
Let's all thank Rick for sharing his story. *clap clap clap*
Group hug!
Well after looking for what was actually causing the out of memory problems, and determining it was just a matter of some necessary beans in Session scope causing the problem, than yes, add more memory etc.
Without using even marginally over-spec'ed servers I have yet to run out of memory, and I tend to store things in session, including shopping carts, whenever it's necessary or convenient to do so.
Maybe it's just because I don't store huge objects in session (in general), but even on a Torque-based app when I keep Torque beans in session I'm still not running out of room. (That's a relatively low-load app, though; it's never been stressed.)
On an internal app at one of my clients, not using torque but more or less plain old beans with specific functionality on a 1G machine with (typically) 500 users connected at any given time I was never in danger of breaking anything, though. (DB hosted on another machine.) Even if I'm storing, say, 100K of crap in the session for each user (which I definitely wasn't), that's 50M of session crap. That's a lot of crap. But it's still like 5% of my memory. (Right? I have a fever today and math cells are the first to go--marked for early swap.) So it's difficult for me to get all worked up about it, especially considering time and maintainence constraints.
Dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
