[
https://issues.apache.org/jira/browse/WICKET-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195927#comment-17195927
]
Tobias Haupt commented on WICKET-6702:
--------------------------------------
[~svenmeier] I don't agree that it has been a completely bad idea. In our
application asynchronous serialization brings a huge performance improvement in
terms of page load times. The serialization of a page takes up to 60ms per
Request. This includes every single ajax-request. We are building a backoffice
application with rather heavy model state and deep/large component tree that
has to be serialized properly.
What i don't fully understand so far is that the *synchronous* serialization
strategy blocks the response from beeing written, flushed and sent to the
client. Wouldn't it be possible to change that, so that the page gets
serialized in the same thread but only after the whole reponse has been sent to
the client?
> 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, 9.0.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)
