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
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
On Thu, Mar 18, 2010 at 11:17 PM, Nigel Parker wrote:
> Thanks for all your help, Johan and Igor. Problem solved we thi
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:
http://wicketstuff.org/maven/repository/o
y way we can persuade Wicket to release the pagemap lock? I have
> > > > looked at the code and this doesn't look straightforward.
> > > >
> > > > - can we get Wicket itself to suppress the StackOverflowError so
so that
>>> detach() continues and releases the lock?
>>>
>>> Grateful for any suggestions.
>>>
>>> Nigel
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache
doesn't look straightforward.
>>
>> - can we get Wicket itself to suppress the StackOverflowError so that
>> detach() continues and releases the lock?
>>
>> Grateful for any suggestions.
>>
>> Nigel
>>
>> -----------------
&
i fixed 2075 so that it should always unlock the pages.
Problem is that you still could get weird errors because that page is not in
a valid state in the session.
So if back buttons/page versions are used it could be that that doesnt work
So what should be fixed is the original problem
On Wed,
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 t
