[MAGNOLIA-1274] memory: recursive activation creates a session per page Created: 15/Dec/06 Updated: 23/Jan/13 Resolved: 10/Oct/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | 3.0.2 |
| Type: | Improvement | Priority: | Critical |
| Reporter: | Philipp Bärfuss | Assignee: | Sameer Charles |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
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) |
| Comments |
| Comment by Sameer Charles [ 15/Dec/06 ] |
|
again its related to 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. thanks for pointing this out |
| Comment by Magnolia International [ 10/Oct/07 ] |
|
this was fixed in 3.0.2 |