Thanks for all your help, Johan and Igor. Problem solved we think. One
of the pages was holding a reference to the session. With multiple
Ajax requests on the same page the session size was doubling each
time, eventually giving stack overflow.
Nigel
Or:
OK, WICKET-2789 added.
Thanks again
Nigel
---
we can modify serializable checker to check if anything is holding a
reference to session or application and catch the error right away. please
add a jira issue for this.
-igor
, Mar 17, 2010 at 21:03, Nigel Parker nigel.par...@mazeppa.no
wrote:
We are a Wicket shop and for one of our clients have been running a
Wicket application successfully for over 2 years. We are now at
version 1.4.0. The traffic on the system is increasing and we are now
seeing an increased
We are a Wicket shop and for one of our clients have been running a
Wicket application successfully for over 2 years. We are now at
version 1.4.0. The traffic on the system is increasing and we are now
seeing an increased frequency of pagemap locking which is beginning to
be a serious problem for