[jira] Updated: (WICKET-1959) PropertyResolver causes memory leaks with proxies

["Gilad Garon (JIRA)" <ji...@apache.org>]

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

Gilad Garon updated WICKET-1959:
--------------------------------

    Description: 
When using proxies for properties, a memory leak occurs.
The ConcurrentHashMap classesToGetAndSetters  doesn't have an eviction policy and fills up with proxies who do not get 
garbage collected.

Build a page which uses proxies as properties, every time a new session is initiated, a new proxy (a new proxy is a new class) of the same property is created and added to the map.
if the proxy is create by a remote jvm you also get a classloader leak.


  was:
When using proxies for properties in wicket a memory leak occurs.
the classesToGetAndSetters ConcurrentHashMap doesn't have an eviction policy and fills up with proxies who do not get 
garbage collected.

Build a page which uses proxies as properties, every time a new session is initiated, a new proxy (a new proxy is a new class) of the same property is created and added to the map.
if the proxy is create by a remote jvm you also get a classloader leak.



> PropertyResolver causes memory leaks with proxies
> -------------------------------------------------
>
>                 Key: WICKET-1959
>                 URL: https://issues.apache.org/jira/browse/WICKET-1959
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.5
>         Environment: All Platforms
>            Reporter: Gilad Garon
>
> When using proxies for properties, a memory leak occurs.
> The ConcurrentHashMap classesToGetAndSetters  doesn't have an eviction policy and fills up with proxies who do not get 
> garbage collected.
> Build a page which uses proxies as properties, every time a new session is initiated, a new proxy (a new proxy is a new class) of the same property is created and added to the map.
> if the proxy is create by a remote jvm you also get a classloader leak.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.