You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Emond Papegaaij (JIRA)" <ji...@apache.org> on 2018/01/30 13:28:00 UTC

[jira] [Resolved] (WICKET-6522) ThreadLocal leak in PageStoreManager

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

Emond Papegaaij resolved WICKET-6522.
-------------------------------------
       Resolution: Fixed
         Assignee: Emond Papegaaij
    Fix Version/s: 7.10.0
                   8.0.0

> ThreadLocal leak in PageStoreManager
> ------------------------------------
>
>                 Key: WICKET-6522
>                 URL: https://issues.apache.org/jira/browse/WICKET-6522
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 7.9.0
>         Environment: Wildfly 10 on CentOS 7 Linux.
>            Reporter: Klaasjan Brand
>            Assignee: Emond Papegaaij
>            Priority: Major
>             Fix For: 8.0.0, 7.10.0
>
>
> One of our heavy-used Wicket production applications has developed 'interesting' behaviour since upgrading to 7.9.0: after a while the system becomes slower and seems to need more CPU time to handle the same amount of requests. Threaddumps exposed that a lot of CPU time was consumed by java.lang.ThreadLocal$ThreadLocalMap.getEntryAfterMiss, pointing to a ThreadLocal leak.
> After making a heapdump (20g) of one of our servers we found lots of ThreadLocalMap$Entry objects referenced by org.apache.wicket.page.PageStoreManager$SessionEntry$1 containing the value Boolean.FALSE.
> Seems that boolean is new behaviour introduced by the fix for WICKET-6465 and is causing complications on servers like Wildfly we use which don't recycle threads.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)