Did you used
getPageSettings().setAutomaticMultiWindowSupport(false);
in your application.java#init method?
This could lower the number of PEE's.
Peter
2009-07-14 20:22 keltezéssel, Martin Makundi írta:
http://issues.apache.org/jira/browse/WICKET-2346
That does not sound like it...
I mean I was getting page expired "for no good reason" unbelievably
often for it to be caused by human error.
I upgraded to rc7, let's see what happens. True, rc4 was working fine before.
**
Martin
2009/7/14 Major Péter<[email protected]>:
Most likely this is it:
http://issues.apache.org/jira/browse/WICKET-2346
Peter
2009-07-14 20:11 keltezéssel, Martin Makundi írta:
Is there a jira issue? I would like to know what it does for the victims
...
**
Martin
2009/7/14 Igor Vaynberg<[email protected]>:
this should be fixed in rc7 - which should be in the maven repo and
most mirrors by now.
-igor
On Tue, Jul 14, 2009 at 10:58 AM, Martin
Makundi<[email protected]> wrote:
Hi!
I have been getting lots of these from our production site since
installing 1.4-rc6? Any idea what it might be?
2009-07-14 20:08:30,879 28612050 [btpool0-108] ERROR RequestCycle -
org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
rendered page in session
[pagemap=null,componentPath=0,versionNumber=2]
org.apache.wicket.protocol.http.request.InvalidUrlException:
org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
rendered page in session
[pagemap=null,componentPath=0,versionNumber=2]
Is it something in Wicket or just a strange user? Why only now and why
does it come up very often?
**
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
