[
https://issues.apache.org/jira/browse/WICKET-7001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Bonn updated WICKET-7001:
-----------------------------------
Description:
We are currently migrating our spring boot Wicket-Application to Kubernetes and
therefore want to cluster our Wicket session.
For that purpose we are using redis (spring-session-data-redis), but the
problem also occurs with other spring-session implementations.
Now we are getting strange behaviours if a page uses a WebSocketBehaviour.
If a page is reloaded with F5 or a behaviour does AjaxTargetRequest.add(page)
the page doesn't work correctly.
We get mutliple errors like (endless loop):
2022-09-02 13:38:48.769 WARN 30020 — [nio-8080-exec-8] RequestCycleExtra
: Handling the following exception
org.apache.wicket.core.request.mapper.StalePageException: A request to page
'[Page class = de.test.pages.TestPage2, id = 12, render count = 1]' has been
made with stale 'renderCount'. The page will be re-rendered.
2022-09-02 13:38:48.769 WARN 30020 — [nio-8080-exec-8] RequestCycleExtra
: ********************************
To our understanding, the renderCount should not have changed, however it is
now 1 instead of 0.
This only occurs if spring-session is enabled AND a WebSocketBehaviour is
beeing used.
I have created a test-project for demonstrating the behaviour:
[https://github.com/chris90763/wicket-session-websocket-error]
we tried different spring-boot versions. 2.6.1, 2.7.0, 2.7.3
Thank you
Christian
was:
We are currently migrating our spring boot Wicket-Application to Kubernetes and
therefore want to cluster our Wicket session.
For that purpose we are using redis (spring-session-data-redis), but the
problem also occurs with other spring-session implementations.
Now we are getting strange behaviours if a page uses a WebSocketBehaviour.
If a page is reloaded with F5 or a behaviour does AjaxTargetRequest.add(page)
the page doesn't work correctly.
We get mutliple errors like (endless loop):
2022-09-02 13:38:48.769 WARN 30020 --- [nio-8080-exec-8] RequestCycleExtra
: Handling the following exception
org.apache.wicket.core.request.mapper.StalePageException: A request to page
'[Page class = de.test.pages.TestPage2, id = 12, render count = 1]' has been
made with stale 'renderCount'. The page will be re-rendered.
2022-09-02 13:38:48.769 WARN 30020 --- [nio-8080-exec-8] RequestCycleExtra
: ********************************
To our understanding, the renderCount should not have changed, however it is
now 1 instead of 0.
This only occurs if spring-session is enabled AND a WebSocketBehaviour is
beeing used.
I have created a test-project for demonstrating the behaviour:
[https://github.com/chris90763/wicket-session-websocket-error]
Thank you
Christian
> wicket with spring-session and websocket
> ----------------------------------------
>
> Key: WICKET-7001
> URL: https://issues.apache.org/jira/browse/WICKET-7001
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 9.11.0
> Environment: standalone and in kubernetes
> Reporter: Christian Bonn
> Priority: Major
>
> We are currently migrating our spring boot Wicket-Application to Kubernetes
> and therefore want to cluster our Wicket session.
> For that purpose we are using redis (spring-session-data-redis), but the
> problem also occurs with other spring-session implementations.
> Now we are getting strange behaviours if a page uses a WebSocketBehaviour.
> If a page is reloaded with F5 or a behaviour does AjaxTargetRequest.add(page)
> the page doesn't work correctly.
> We get mutliple errors like (endless loop):
> 2022-09-02 13:38:48.769 WARN 30020 — [nio-8080-exec-8] RequestCycleExtra
> : Handling the following exception
> org.apache.wicket.core.request.mapper.StalePageException: A request to page
> '[Page class = de.test.pages.TestPage2, id = 12, render count = 1]' has been
> made with stale 'renderCount'. The page will be re-rendered.
> 2022-09-02 13:38:48.769 WARN 30020 — [nio-8080-exec-8] RequestCycleExtra
> : ********************************
> To our understanding, the renderCount should not have changed, however it is
> now 1 instead of 0.
> This only occurs if spring-session is enabled AND a WebSocketBehaviour is
> beeing used.
> I have created a test-project for demonstrating the behaviour:
> [https://github.com/chris90763/wicket-session-websocket-error]
>
> we tried different spring-boot versions. 2.6.1, 2.7.0, 2.7.3
> Thank you
> Christian
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
