Description
Something has changed in the way pages are serialized in wicket 9.x thus that if a page has a reference to session serialization enters in a loop causing an stack overflow. See attached project. While there is no reasons to keep a reference to session, and I have fixed that in our legacy code causing this problem, it would be nice to avoid server crashing because of this (and log a huge warning for users to note).
Attachments
Attachments
Issue Links
- fixes
-
WICKET-6847 async page storing fails with flush before detach without session
- Resolved