wicket-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Makundi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (WICKET-5805) Non blocking page serialization (fixme: session leak)
Date Thu, 08 Jan 2015 07:24:34 GMT

     [ https://issues.apache.org/jira/browse/WICKET-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Martin Makundi updated WICKET-5805:
-----------------------------------
    Attachment: patch-serialize.txt

Proposed patch, but has critical session leak issue.

> 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.4#6332)

Mime
View raw message