[
https://issues.apache.org/jira/browse/WICKET-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975279#action_12975279
]
Johan Compagner commented on WICKET-1973:
-----------------------------------------
you really should use sticky sessions,
I dont see any reason not to use that, and it is way better for performance.
A browser can do many request at the same time to the server, those should hit
the same node, else you have multithreaded access to pages over multiply
computers. What is then the final page that you want to have?
> Messages lost upon session failover with redirect_to_buffer
> -----------------------------------------------------------
>
> Key: WICKET-1973
> URL: https://issues.apache.org/jira/browse/WICKET-1973
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4-RC1
> Reporter: Erik van Oosten
>
> Using the redirect_to_buffer render strategy, messages in the session get
> cleared after the render.
> If the redirected request comes in at another node, the buffer is not found
> and the page is re-rendered. In this case the messages are no longer
> available.
> See the javadoc of WebApplication#popBufferedResponse(String,String).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
