It's all about the answers!

Ask a question

RAMSession server side session allocation

Stephen Schmidt (1142) | asked May 24 '10, 2:07 p.m.
Within an application that we have that uses the RAM public api, we are encountering situations where we easily hit the per-user session limit (10) when attempting to share the use of an allocated RAMSession object. The pattern we have noticed is that within our multi-tabed web application, if we navigate to another tab within the application and then navigate back to the tab that we initiate RAM activity from, another server side session is being allocated. We have validated through tracing that we are not explicitly allocating another client side RAMSession object, but we are seeing the server side connections growing consistently. Is there something we can do to allow this session sharing ??

One answer

permanent link
Kevin Bauer (34621) | answered May 24 '10, 5:07 p.m.
One thing to be aware of is that if you do not call RAMSession.release() after you are finished with a session your server will hold on to your session for 30 minutes.

Using calls from the same RAMSession object does use the same session and should not be eating up server side sessions.

Your answer

Register or to post your answer.