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.
Once the user has clicked a link to another page (Or switched a tab if it is
a tabed page), is there a way to terminate the request to prevent a load on
the server for a page that will not be displayed?
Normally: no, because these are separate requests. The first request will
cancel only when
-wicket.1842946.n4.nabble.com/PageMap-locking-tp3930623p3932536.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h
to the discussion
below:
http://apache-wicket.1842946.n4.nabble.com/PageMap-locking-tp3930623p3932536.html
To unsubscribe from Apache Wicket, click
herehttp://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=1842946code
How can i delegate to another PageMap when i need it on a panel in a tabed
page?
The PageMap is declared in the page, how can i use a diffrent PageMap for a
tab in the page?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/PageMap-locking-tp3930623p3932904.html
Sent
to the page map to be
relased...)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/PageMap-locking-tp3930623p3930623.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe
, is there a way to go to another tab without waiting for the
first tab to rendered? (As the tab link is waiting to the page map to be
relased...)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/PageMap-locking-tp3930623p3930623.html
Sent from the Users forum mailing list
Hi all,
hoping to get some debugging tips on a concurrency issue I've run into.
What we're seeing is concurrent access to a Page instance, when our
application is under a lot of stress.
The backend is taking a lot of time, which should be handled by Wicket by
locking on the pagemap. This is
most likely this concurrent access happens when you are iterating over
pages in the pagemap and invoking listeners on them and another thread
access one of the pages you are iterating over. you will have to lock
your iteration loop on the same lock wicket uses. as a rule of thumb
we do not
yeah, that's why I thought that I would be safe when only dispatching events
during the request processing to a page from the page-map.
thanks, Frank
On Wed, Apr 28, 2010 at 4:48 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
most likely this concurrent access happens when you are iterating
)
Since we have changed to production mode we are facing very often with pagemap
locking errors which is big annoyance.
I have increased the timeout value using
getRequestCycleSettings().setTimeout(Duration.minutes(10)), which isn't a
solution.
The problem ist that long running requests block
often with
pagemap locking errors which is big annoyance.
I have increased the timeout value using
getRequestCycleSettings().setTimeout(Duration.minutes(10)), which isn't a
solution.
The problem ist that long running requests block new requests (some requests
running undefinitely long
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
14 matches
Mail list logo
