[
https://issues.apache.org/jira/browse/WICKET-6845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219042#comment-17219042
]
Sven Meier commented on WICKET-6845:
------------------------------------
+1 The prevention of the serialization-loop is a good trick.
I've changed another thing though: The session cache of
DefaultPageManagerProvider does not need to serialize pages on session
serialization anyway. They can be acquired from any other persistent store
instead. This is something I've got wrong when restructuring page stores for
Wicket 9.x - this is why this stack-overflow is not happening on 8.x
> stackoverflow while serializing a page containing a reference to session
> ------------------------------------------------------------------------
>
> Key: WICKET-6845
> URL: https://issues.apache.org/jira/browse/WICKET-6845
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 9.0.0, 9.1.0
> Reporter: Ernesto Reinaldo Barreiro
> Assignee: Martin Tzvetanov Grigorov
> Priority: Major
> Attachments: session-serialization.tar.gz
>
>
> 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).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
