Our webapp running on Resin-pro 3.0.21 uses Wicket 1.2.4.
Our server often gets saturated with open file connections.
When checking this with lsof, we see that the Wicket.jar file is getting
loaded many times. i.e. once per every hit to our webapp.
This fills up the open file space on our RHEL s
Thank you again.
I did as u said. Removed the self updating thing.
But still the pages are expiring all over the place.
Anything else I can try?
--
View this message in context:
http://www.nabble.com/Expiring-Pages-tf2946013.html#a8278080
Sent from the Wicket - User mailing list archive at Nab
Thank you!
I put the following code in the constructor of my web-pages.
add(new AjaxSelfUpdatingTimerBehavior(Duration.minutes(10)));
add(new AbstractAjaxTimerBehavior(Duration.minutes(10))
{
/**
* @see
wicket.ajax.
Thank you!
I put the following code in the constructor of my web-pages.
add(new AjaxSelfUpdatingTimerBehavior(Duration.minutes(10)));
add(new AbstractAjaxTimerBehavior(Duration.minutes(10))
{
/**
* @see
wicket.ajax.
Thank you for ur prompt reply.
I did set
120
4096
and
120
false
in the as well.
But that seems to have no effect.
I tested this by setting the timeout to 1 in both places, restarting resin,
loading a web
We have a web-app which deals with online hotel bookings, which uses Wicket
1.2.4.
We have a problem with the pages expiring, when refreshed or submitted, in
after about 20 min of inactivity.
This also happens when Back button is clicked from a page.
We need to have the pages not-expire for about
