Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
With servlets/jsp, can sessions be recycled by the web container (say tomcat), depending on how much traffic a site is getting?
Update
By recycled I mean, the tomcat container will wipe it out since it is running out of memory or busy trying to server requests for another website on the same server
This happens with IIS and .net
According to the API specification, a servlet container is not allowed to invalidate or delete a session before the session timeout is reached (it is however allowed to keep it longer than the session timeout). To cope with a high number of simultaneous sessions, most servlet containers can be configured to persist sessions to disk or to a database, allowing the container to free memory, but still being able to restore the session later if it is required. It is therefore required by the specification that all objects stored in the session must be serializable, although most servlet containers (also Tomcat) do not check this explicitly.