[MAGNOLIA-5689] Make ActivationMonitorPage more fail-safe Created: 18/Feb/14 Updated: 27/Feb/14 Resolved: 27/Feb/14 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | None |
| Fix Version/s: | 4.5.17 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Zdenek Skodik | Assignee: | Christoph Meier |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| 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
|
||||
| Date of First Response: | |||||
| Description |
|
The default ActivationStorage implementation holds all informations in memory, it might happen that some of them are gone when ActivationMonitorPage tries to fetch them (i.e. if one recreates the Inbox workspaces from scratch and a strict garbage collection is performed). In order to not display freemarker errors when one tries to access the page, we could improve null handling. |
| Comments |
| Comment by Roman Kovařík [ 27/Feb/14 ] |
|
Still fails with with the same error: ==> assignment: subscriber=subscribers[entry] [on line 199, column 11 in info/magnolia/module/exchangesimple/pages/ActivationMonitorPage.html] To reproduce add this code to info.magnolia.module.exchangesimple.monitor.ActivationMonitor: @Override
public Map<String, ResponseTimeEntry> getSubscriberResponseTimes() {
Map map = new HashMap<String, ResponseTimeEntry>();
map.put("key", null);
return map;
}
|