[jira] [Commented] (WICKET-5805) Non blocking page serialization (fixme: session leak)

["Martin Makundi (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969825#comment-15969825 ] 

Martin Makundi commented on WICKET-5805:
----------------------------------------

Fixed with https://issues.apache.org/jira/browse/WICKET-6177

> Non blocking page serialization (fixme: session leak)
> -----------------------------------------------------
>
>                 Key: WICKET-5805
>                 URL: https://issues.apache.org/jira/browse/WICKET-5805
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.4.23
>            Reporter: Martin Makundi
>            Priority: Critical
>         Attachments: patch-serialize.txt
>
>
> We have a performance issue with our Wicket 1.4 app, page serialization causes inconvenience to user because RequestCycle.detach() blocks the request until session.requestDetached() has been handled.
> We attempted to solve this issue by invoking session.requestDetached in a separate thread and thus allowing user to receive their request without waiting for page serialization in SecondLevelCachePageMap. The disk writing is already parallel, but serialization is blocking.
> What would be the best way to implement this? I have attached our (proposed) patches.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)