[
https://issues.apache.org/jira/browse/WICKET-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195353#comment-17195353
]
Emond Papegaaij commented on WICKET-6702:
-----------------------------------------
This issue is still valid in 9.1.0-SNAPSHOT. I'm hitting this bug as well. I
think there're 2 possible solutions to this:
* Acquire a lock on the page in {{AsynchronousPageStore}} to prevent concurrent
modifications in a request.
* Serialize synchronously and then delegate to {{AsynchronousPageStore}}, so
switch the order of the 2 stores.
I can reproduce the problem quite reliably on one of the pages in our
application (like once every 3 hits). In our case the ArrayList is the children
list of a component.
> AsynchronousPageStore with NotDetachedModelChecker - "Not detached model
> found" exception on several fast sequential Ajax calls
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-6702
> URL: https://issues.apache.org/jira/browse/WICKET-6702
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 8.5.0
> Reporter: Sergei Tkachuk
> Priority: Major
> Attachments: QuickStart.zip
>
>
> Preconditions: Application uses AsynchronousPageStore (as it is by default).
> When there are several fast sequential Ajax calls to a component, then a
> component's LoadableDetachableModel gets attached and detached several times
> before real async serialization takes place. And at times the serialization
> is initiated when the model has been already attached once again by a
> subsequent Ajax call, and not detached yet as the request is still in
> progress. This causes NotDetachedModelChecker() to throw "Not detached model
> found!" exception
> Disabling async serialization fixes the problem.
> A test-case and a log attached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
