Forgive my lack of understanding of Wicket internals, but do requests for
Ajax components on a particular page block when that page is being
serialized?
Matej Knopp-2 wrote:
>
> This really looks like page being accessed from multiple threads, but
> it's quite weird. The serialization is done i
This really looks like page being accessed from multiple threads, but
it's quite weird. The serialization is done in request thread and
pagemap is locked during request.
-Matej
On Thu, Dec 18, 2008 at 2:35 PM, leok wrote:
>
> Interesting. I wonder if this error occurs when page components are be
Interesting. I wonder if this error occurs when page components are being
modified by Ajax while being serialized, e.g. page.addOrReplace(). If so,
this is kind of an ugly bug. What I don't know yet is how "harmful" this bug
is, i.e. does this error leave Wicket in a horribly inconsistent state?
Same symptoms using wocket 1.4-rc1.
Regards
Alexandre
leok wrote:
>
> I was poking through some logs, and I noticed a few rare instances of this
> exception:
>
> java.util.ConcurrentModificationException
> at
> java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:365)
>
I was poking through some logs, and I noticed a few rare instances of this
exception:
java.util.ConcurrentModificationException
at
java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:365)
at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:376)
at java.util.Ha
