You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sven Meier (Jira)" <ji...@apache.org> on 2020/10/22 12:59:00 UTC
[jira] [Comment Edited] (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=17218988#comment-17218988 ]
Sven Meier edited comment on WICKET-6845 at 10/22/20, 12:58 PM:
----------------------------------------------------------------
[~mgrigorov] I think your commit with regarding the AsynchronousPageStore and HTTP session belongs to WICKET-6702 and the comment from [~reiern70]
I think this is a good solution and we should create a separate issue for 9.2.0 for that.
was (Author: svenmeier):
[~mgrigorov] I think your commit with regarding the AsynchronousPageStore and HTTP session belongs to WICKET-6702 and the comment from [~reiern70]
> 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)