The answer to the (completely rhetorical) question is probably yest, but I've got another question, too.
So, I have this moderately large application with jsps, servlets, and an Oracle DB. It does its thing ok, but it never releases memory. There are certainly session variables (probably way too many, but that's (hopefully) a question for another day), but even after the session expires, I'm still using the same amount of memory. I even included a direct call to System.gc() on my first page, hoping to collect the memory from the three day old sessions, but no luck. So, my thoughts/questions: Some connections are still opened (this is what's running on my development server right now: however, the actual development is done in Sun ONE on my desktop, so I'm going through and making sure all of those are closed there... but I'm also trying to debug this memory issue), so maybe these open connections force some of the session scoped beans to persist? Forever? Or am I just missing something completely about garbage collection? So, in short, if I have a session scoped bean that has in it something like a connection or a recordset (which is most likely not a good idea... I now know that), even after the session times out, would that bean continue to exist? And eat up my memory? Sorry for the rambling. Michael Nicholson, Carolina Center for Public Service
