-
Bug
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Yes
-
UI FW 6, Maintenance 19
-
5
Some analysis:
- a corrupted (un-populated/empty) message ends up in a message store
- the message marshaller fails to parse it and throws an exception
- exception bubbles in admincentral and eventually causes another error message to be sent, which in turn causes the app to refresh own views
- -> rinse repeat...
Acceptance criteria