[MAGNOLIA-6886] NullPointerExceptions in PersonalizedNodeRenderingListener in ERROR requests Created: 25/Nov/16 Updated: 25/Nov/16 Resolved: 25/Nov/16 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 5.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jarkko Mantysaari | Assignee: | Unassigned |
| Resolution: | Duplicate | 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)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Description |
|
Rendering the error page when request has been initiated with the ERROR dispatcher causes NullPointerExceptions in PersonalizedNodeRenderingListener. It seems that the WebContext somehow disappears when the error request is handled. CacheFilter plays some role here because if it is disabled, then everything is working fine. Part of the stacktrace: java.lang.NullPointerException |