You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Tzvetanov Grigorov (Jira)" <ji...@apache.org> on 2020/10/20 12:10:00 UTC
[jira] [Commented] (WICKET-6845) stackoverflow while serializing a
page containing a reference to session
[ https://issues.apache.org/jira/browse/WICKET-6845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17217551#comment-17217551 ]
Martin Tzvetanov Grigorov commented on WICKET-6845:
---------------------------------------------------
We have [https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/core/util/objects/checker/SessionChecker.java] for "logging a huge warning".
Maybe it should be enabled by default in DEV mode ?!
> 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
> 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)