×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: Thorbjoern Ravn Andersen
One way to approach this, is to kill idle sessions ...
Of course. Session data and objects may be consuming a lot of memory. And it might make sense to release it after a period of inactivity - depending on the application. But what I was hoping that you might explain is whether that's a function of the application that the developer must code, or part of a framework, or some sort of configuration setting in an application server? An optional setting for each application, or JSP, or Servlet, or Session Manager, or whatever?
Another approach used AFAIK in Apache Tomcat and other
Java web servers is to persist the oldest sessions to disk ...
And the same questions apply here. Code that into the application? Use a framework? A configuration setting in Tomcat? Does serializing an object automatically release memory?
Thanks,
Nathan.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
