[
https://issues.apache.org/jira/browse/WICKET-6845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17217907#comment-17217907
]
ASF subversion and git services commented on WICKET-6845:
---------------------------------------------------------
Commit 8664176abcc6393c54b29d058c655d440500bc8d in wicket's branch
refs/heads/master from Martin Tzvetanov Grigorov
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=8664176 ]
WICKET-6845 stackoverflow while serializing a page containing a reference to
session
Make sure an HTTP session is created before committing the response.
This is needed because org.apache.wicket.pageStore.RequestPageStore#detach() is
called after committing the response and it is too late to create an HTTP
session at that time.
> 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)
