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

Posted to commits@wicket.apache.org by "Wolfgang Kritzinger (JIRA)" <ji...@apache.org> on 2012/10/17 17:02:03 UTC

[jira] [Updated] (WICKET-4820) Race condition in ResourceSettings: getResourceWatcher() is not thread safe

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

Wolfgang Kritzinger updated WICKET-4820:
----------------------------------------

    Attachment: WICKET-4820.zip

Quickstart that contains the test TestModificationWatcherRaceCondition that can reproduce the problem
                
> Race condition in ResourceSettings: getResourceWatcher() is not thread safe
> ---------------------------------------------------------------------------
>
>                 Key: WICKET-4820
>                 URL: https://issues.apache.org/jira/browse/WICKET-4820
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.8, 6.1.1
>            Reporter: Wolfgang Kritzinger
>            Priority: Minor
>         Attachments: WICKET-4820.zip
>
>
> o.a.w.settings.def.ResourceSettings.getResourceWatcher() is not thread safe: when multiple requests are waiting to load markup for the first time (for example, start "ab" with -c 40 right after starting the wicket application) multiple ModificationWatcher threads are started which cause a memory leak when the WicketApplication is stopped.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira