[MAGNOLIA-2159] session can be closed if LazyContentWrapper is used Created: 28/May/08 Updated: 23/Jan/13 Resolved: 28/May/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.5.7, 3.6 |
| Fix Version/s: | 3.5.8, 3.6 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
It is the nature of the LazyContentWrapper to refetch the wrapped node again if the session has been closed. That is fine. If you then access children later it might be that the former session has been closed because it has been handled by another thread:
|
| Comments |
| Comment by Philipp Bracher [ 28/May/08 ] |
|
This brings us back to the discussion about using shared sessions for the system context. This might be OK as we have to keep sessions for the observation anyway |
| Comment by Philipp Bracher [ 28/May/08 ] |
|
I have been able to fix the issue. I will think about moving back to SingleJCRSessionSystemContext |