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 reach at least 50 to 100
clicks.
Example: let's say DashboardPage, PersonProfilePage, AddressPage,
EmploymentRelatedPage, SomeXYZPage from the Home Page or somewhere from the
application. Just load them simultaneously
Wicket 5 PageStoreManager preserves certain number of page versions and
destroying others from its List. If your application
stores those pages in List then they may not be available
in your session ( in heavy load). Debug “PageStoreManager” for more
details.
Try the below code snippet where your application expecting page from the
session if the above scenario helps you to reproduce the issue.
if (Session.get().getPageManager().getPage(page.getPageId()) == null) {
Session.get().getPageManager().touchPage(page);
}
Or (preserves always)
Session.get().getPageManager().touchPage(page);
On Sun, Sep 24, 2017 at 3:02 AM, trlt wrote:
> 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 intermittently
> and
> only happens to a handle of users which makes the debugging harder.
>
> Any suggestion is greatly appreciated. Thanks!
>
> --
> Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-
> f1842947.html
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
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 intermittently and only happens to a handle of users which makes the debugging harder. Any suggestion is greatly appreciated. Thanks! -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
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. 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? -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
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? -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
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 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. My program redirects them to a bookmarkable page, and off they go. However, I noticed this week when this happens, some users get into the infinite loop of "Page Expired" errors. All the links they access (bookmarkable or non-bookmarkable), they all throw "PageExpiredException" error. When users complain, I can often access those pages without any issues. This makes it hard for me to debug. The only way for the users to get out of the loop is by clearing their browser's cache (even the logout link becomes stale at this point). Nothing has changed in my session implementation so I'm a bit puzzled by this. Can someone shed some light on this for me? -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
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. My program redirects them to a bookmarkable page, and off they go. However, I noticed this week when this happens, some users get into the infinite loop of "Page Expired" errors. All the links they access (bookmarkable or non-bookmarkable), they all throw "PageExpiredException" error. When users complain, I can often access those pages without any issues. This makes it hard for me to debug. The only way for the users to get out of the loop is by clearing their browser's cache (even the logout link becomes stale at this point). Nothing has changed in my session implementation so I'm a bit puzzled by this. Can someone shed some light on this for me? -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
