Though I am using 'ONE_PASS_RENDER' strategy, I am still getting the below
warning,
WARN http-8000-2 [org.apache.wicket.request.handler.render.WebPageRenderer]
- Falling back to Redirect_To_Buffer render strategy because none of the
conditions matched.
Am I missing something? I am worried that
Hi,
If you cannot use sticky sessions then you should not use
REDIRECT_TO_BUFFER because the pre-rendered response is saved/buffered
in the WebApplication on the current node and there is a (big) chance
that the next request wont be processed by the same node.
You can use either ONE_PASS_RENDER
Thanks Martin for the response. Could you please answer the below question as
well?
What is the use of the below API?
getRequestCycleSettings().setBufferResponse(false);
Does it make any difference to the render strategy? I guess it makes some
difference to 'REDIRECT_TO_BUFFER'.
Thanks,
No, this is not related.
I just improved its javadoc:
https://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=commitdiff;h=43878fc8c470044923f3b599953a1c4ff2aef63b
Is it cleaner now ?
On Wed, Aug 22, 2012 at 2:15 PM, sudeivas sureshkumar@gmail.com wrote:
Thanks Martin for the
Yes it is. Thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Which-RENDER-STRATEGY-is-best-for-clustered-setup-tp4651420p4651433.html
Sent from the Users forum mailing list archive at Nabble.com.
Hello,
We are currently using Apache Wicket 1.5.6 in a clustered setup. We
have a custom built distributed session management based on memcached. Due
to infrastructure limitations, we cannot use sticky sessions. So I am
wondering whether 'ONE_PASS_RENDER' render strategy is the best
