[
https://issues.apache.org/jira/browse/WICKET-6847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17227324#comment-17227324
]
Emond Papegaaij commented on WICKET-6847:
-----------------------------------------
I think I know the cause of the problem. The check [~mgrigorov] added in
https://github.com/apache/wicket/commit/8664176abcc6393c54b29d058c655d440500bc8d
is done at a moment when we cannot always know if the page is stateless or
not. One of the locations it is called from is {{onInitialize}}, at which point
the page very likely does not hold any components yet. On thing I do find
strange though, is that I consistently get a second call from
{{onAfterRender}}, at which point the session is also created. [~reiern70]
could it be that you are instantiating pages without actually rendering them?
> async page storing fails with flush before detach without session
> -----------------------------------------------------------------
>
> Key: WICKET-6847
> URL: https://issues.apache.org/jira/browse/WICKET-6847
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 9.1.0
> Reporter: Sven Meier
> Assignee: Martin Tzvetanov Grigorov
> Priority: Minor
> Fix For: 9.2.0
>
>
> Since WICKET-6831 the response is flushed before detach.
> RequestPageStore delays storing all of stateful pages until detach; at that
> moment AsynchronousPageStore can no longer acquire the required session id.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
