Re: Wicket 1.5 PageExpiredException

Is it happening in all the browsers? Have you tried the scenarios as given below in your application to reproduce the same issue in your machine or the development server? Scenario: Open certain set of application pages simultaneously by clicking the links (other links), do not stop until you

Re: Wicket 1.5 PageExpiredException

The wicket applications are authenticated using Single Sign On (so yes, there are other cookies set by the SSO group). The Bookmarkable links seem to be working fine, but all other links become expired. Again, the only way to get out is to clear the browser's cache. This problem happens

Re: Wicket 1.5 PageExpiredException

Must be something in the session then. What's your authentication setup? Do you use additional cookies besides the session cookie? Sven Am 23.09.2017 um 00:39 schrieb trlt: Apache + Tomcat. No load balancer. In general, I guess I have to understand how pages are re-created once expired.

Re: Wicket 1.5 PageExpiredException

Apache + Tomcat. No load balancer. In general, I guess I have to understand how pages are re-created once expired. The problem seems to be specific to the cache in user's browser as I don't have problem when accessing the same pages. Why did clearing the browser's cache fix the problem? --

Re: Wicket 1.5 PageExpiredException

What's your server setup? Do you have a load balancer in front of your web containers? Sven Mit AquaMail Android http://www.aqua-mail.com gesendet Am 22. September 2017 19:24:06 schrieb trlt : I have a set of applications written in wicket (1.5.10) that have been running

Wicket 1.5 PageExpiredException

I have a set of applications written in wicket (1.5.10) that have been running for 5+ years without any issues, but recently I've encountered some problems that I've never seen before: This problem has to do with PageExpiredException. In the past, the user hit a page, got a "Page Expired" error.