[ http://jira.magnolia.info/browse/MAGNOLIA-1274?page=comments#action_13065 ] Sameer Charles commented on MAGNOLIA-1274: ------------------------------------------
again its related to MAGNOLIA-1221 I will implement it together, option (a) is the best solution since its not only HTTP session which is a problem but JCR session does not release memory after importing data. it wont make sence to implement only to solve one problem since we can easily maintain transations here. thanks for pointing this out > memory: recursive activation creates a session per page > ------------------------------------------------------- > > Key: MAGNOLIA-1274 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1274 > Project: Magnolia > Issue Type: Improvement > Components: activation > Affects Versions: 3.0.1 > Reporter: Philipp Bracher > Assigned To: Sameer Charles > Priority: Critical > Fix For: 3.0.x > > > Each page is sent by a atom package/request to the public instance, where per > request a session is created. We should implement one of these solutions: > a) reuse the session id returned by the first request (no relogin after each > request) > b) invalidate session after the execution (simple) > c) don't use session at all (needs more work, since we use the session to > login) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
