Hi,
A user was testing a web application.
Apparently they clicked on a link that opened a report and quickly
clicked the link again.
The web application became unusable and tomcat had to be restarted.
If the issue was a long request time ( perhaps something was going on
with the database at
this has been discussed many times on the list, search the archives...
-igor
On Wed, Dec 14, 2011 at 9:20 AM, Karen Schaper karen.scha...@gmail.com wrote:
Hi,
A user was testing a web application.
Apparently they clicked on a link that opened a report and quickly
clicked the link again.
Hi all,
i'm developing a wicket application, in which i have to lookup mutiple tables
with millions of datasets depending of the user inputs.
Any operation on these tables is very time consuming not to talk about join
operations ... (A request can take a few seconds or some minutes to
Why would you want your users to wait for 1 minute to get results? On
what planet and time/space continuum do you expect users to wait for
that?
Don't do the computation in the request thread. Compute the stuff in a
separate thread, process or whatever and subscribe the user's
Thanks for your feedback Martijn.
Yes, you're right. I will solve this issue using threads.
Von: Martijn Dashorst martijn.dasho...@gmail.com
An: users@wicket.apache.org
Gesendet: Donnerstag, den 23. April 2009, 10:59:39 Uhr
Betreff: Re: Pagemap locking issue
