[
https://issues.apache.org/jira/browse/WICKET-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17075879#comment-17075879
]
Sven Meier commented on WICKET-6702:
------------------------------------
Hi [~thorben.schmidt] ,
all pages are single-threaded by design, Wicket uses PageAccessSynchronizer to
enforced this.
This includes Ajax requests, which are processed sequentially on each page.
We will have to lock the page while it is serialized asynchronously. otherwise
ConcurrentModificationException can happen on all sort of places.
Obviously this would delay any further requests on the same page.
> 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)
