_RENDER);
- setting setAutomaticMultiWindowSupport to true adds the following to new
urls: "/wicket:pageMapName/wicket-3/". Is there any way to prevent this
as it mangles the URL effect I am trying to implement?
--
View this message in context:
http://apache-wicket.1
On Thu, Jul 1, 2010 at 2:30 AM, sbrookes2 wrote:
> It turns out that isn't the only source of these messages as it seems to be
> related to using AJAX behaviors on stateless pages causing the pagemap to
> either lose or remove references to certain pages so that when an AJAX
> request comes in the
us for a couple of years but now that I am
trying to implement a 'real' fix I am concerned I may have made a big
architecture mistake given the heavy emphasis on state with Wicket.
Hopefully there is a magic bullet out there someone can share.
Thanks,
Sean
--
View this message in co
We're interested in this as well, as our logs are full of these as well.
On Mon, Apr 12, 2010 at 10:32 AM, Nikita Tovstoles
wrote:
> So far I traced this down to the fact that sometimes some wicket:interface
> requests (in our case used in img src and in anchor 'href) do not include a
> jsession
So far I traced this down to the fact that sometimes some wicket:interface
requests (in our case used in img src and in anchor 'href) do not include a
jsessionid - either as a ";jsessionid=" URL param or a cookie - thus no
session can be found.
The container's impl of HttpServletResponse.encodeURL
Here's a typical exception:
00:01:17,644 ERROR CLPWebRequestCycle:34 - Cannot find the rendered
page in session
[pagemap=null,componentPath=7:results:resultsInfo:criteriaContainer:inputPanel:categorySearchForm:submitLink:searchButton,versionNumber=0]
org.apache.wicket.protocol.http.PageExpiredExce
We're seeing a PageExpiredExceptions in roughly 2-6% of our production web
sessions and cannot determine the root cause:
1. it's not a session affinity problem (we went as far as running a
single node - the exceptions persisted)
2. it's not a session expiration case (our avg production se
