Re: Overwhelming a Web Application Server

[Pete Helgren <Pete@xxxxxxxxxx>]

My experience, so far, is that all of the session handling/management of 
the servlet container is adequate for what I need.  But in my case, I 
don't have thousands, or even hundreds of concurrent hits so perhaps my 
lack of attention to this particular area will come back to haunt me if 
I get hundreds or thousands of users (a problem I look forward to).

I keep the session timeout value relatively low so that sessions expire 
and are GC'ed on a regular basis and, although I think that I don't 
carry too much information around in the session itself, this thread has 
reminded me that I need to profile my servlet on Tomcat and see how it 
performs, especially when it comes to memory utilization.

It has been a good discussion, and timely.

Pete



Nathan Andelin wrote:
> > From: Bradley V. Stone
> > But again I'd guess in most cases that ID is stored in DB file(s) and
> > looked up on each request, not in memory.
> >     
>
>
> I bet a lot of RPG-CGI programs use DB files to store session data, but I get the impression that Java objects are "serialized" to stream files, and typically larger - a developer may dump an SQL result set to a "collection" and store it in a "session", for example.  Maybe it depends on the application.
>
> Nathan.
>
>
>
>       
>