You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Martin Makundi <ma...@koodaripalvelut.com> on 2015/01/09 15:16:05 UTC

Re: Session leak issue, trying to optimize 1.4x

Hi!

Can anybody help with this?
https://issues.apache.org/jira/browse/WICKET-5805

**
Martin

2015-01-08 9:24 GMT+02:00 Martin Makundi <martin.makundi@koodaripalvelut.com
>:

> Hi!
>
> 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 (and safest) way to implement this? I have attached
> our (proposed) patches to jira issue:
> https://issues.apache.org/jira/browse/WICKET-5805
>
>
> **
> Martin
>

Re: Session leak issue, trying to optimize 1.4x

Posted by Martin Makundi <ma...@koodaripalvelut.com>.
Bounty:
https://www.elance.com/j/java-wicket-core-jetty-internals-expert-fix-session-leak-issue/67287632/

2015-01-09 16:16 GMT+02:00 Martin Makundi <
martin.makundi@koodaripalvelut.com>:

> Hi!
>
> Can anybody help with this?
> https://issues.apache.org/jira/browse/WICKET-5805
>
> **
> Martin
>
> 2015-01-08 9:24 GMT+02:00 Martin Makundi <
> martin.makundi@koodaripalvelut.com>:
>
>> Hi!
>>
>> 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 (and safest) way to implement this? I have
>> attached our (proposed) patches to jira issue:
>> https://issues.apache.org/jira/browse/WICKET-5805
>>
>>
>> **
>> Martin
>>
>
>