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.
We are looking to implement in memory session replication. Before we do that our main concern is how the session objects will use the memory? and if session get large after some time will get out of memory error so how to overcome this other than increasing the memory size?
if anybody get into these please reply me.., Thanks in advance.
One thing you can do is limiting the number of active sessions (maxActiveSessions): http://tomcat.apache.org/tomcat-7.0-doc/config/manager.html#Common_Attributes – so you can limit the memory used by sessions.
Another option is to use non-sticky sessions so that there are only as much sessions concurrently stored in memory as there are concurrent requests. Not sure about the details of the tomcat integrated replication of with non-sticky sessions, but at least memcached-session-manager can manage them (I must mention that I’m the author of this lib). It also provides jmx statistics that allow you to inspect the session memory size.