[jira] [Assigned] (WICKET-6633) Adding CryptoMapper as RootRequestMapper results in OutOfMemoryError.

["Martin Grigorov (JIRA)" <ji...@apache.org>]

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

Martin Grigorov reassigned WICKET-6633:
---------------------------------------

    Assignee: Martin Grigorov

> Adding CryptoMapper as RootRequestMapper results in OutOfMemoryError.
> ---------------------------------------------------------------------
>
>                 Key: WICKET-6633
>                 URL: https://issues.apache.org/jira/browse/WICKET-6633
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 8.2.0
>            Reporter: Joris van Heesch
>            Assignee: Martin Grigorov
>            Priority: Major
>
> I created a simple Wicket reproducer, starting from a Wicket Quickstart.
> The reproducer consists of the following:
>  - HomePage
>  - stylesheet.css, used in HomePage via response.render(CssHeaderItem.forReference(...)).
>  - MimicBrowserPageLoads: a simple java application (main method) that mimics browser requests to HomePage: it does 1 GET request for the html, and 1 GET for the css. It does this 100.000 times, clearing the cookies after each 'page load'.
> h2. The problem
> When I remove the CryptoMapper and start jetty using the quickstart's code, adding -Xms64m -Xmx64m, all works fine: I can run MimicBrowserPageLoads, and no problems arise.
>  However, when I configure CryptoMapper as the application's RootRequestMapper and start jetty, again adding -Xms64m -Xmx64m, starting MimicBrowserPageLoads will, after some time, result in OutOfMemoryError for the jetty process.
> The reproducer can be found here: [https://github.com/jvanheesch/cryptomapper-outofmemoryerror]
> The same problem occurs when deploying with Tomcat 9.0.14.



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