You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Rob Audenaerde (JIRA)" <ji...@apache.org> on 2013/04/17 14:33:15 UTC

[jira] [Comment Edited] (WICKET-5147) WicketTester MockHttpRequest.getCookies very slow / OutOfMemory

    [ https://issues.apache.org/jira/browse/WICKET-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633978#comment-13633978 ] 

Rob Audenaerde edited comment on WICKET-5147 at 4/17/13 12:32 PM:
------------------------------------------------------------------

The test 'changeLabelTwoTimes' test will fail. The number of cookies in the request will be 16 after the first call (too much already) and is 64 after the second call. 
I would expect them to be 1.


                
      was (Author: robau):
    The test 'changeLabelTwoTimes' test will fail. The number of cookies will be 16 after the first call (too much already) and is 64 after the second call. 
I would expect them to be 1.


                  
> WicketTester MockHttpRequest.getCookies very slow / OutOfMemory
> ---------------------------------------------------------------
>
>                 Key: WICKET-5147
>                 URL: https://issues.apache.org/jira/browse/WICKET-5147
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 6.7.0
>            Reporter: Rob Audenaerde
>         Attachments: testcookies.zip
>
>
> We have an extensive set of WicketTester tests. Recently, the wicket RELEASE in the maven repository changed to 6.7.0. After the new version, our tests got very slow.
> When profiling, I discovered that the MockHttpRequest.getCookies() was taking up a lot of time. Also, tests failed because of OutOfMemory exceptions. My guess is that somehow a lot of objects are created at such speeds that the GC cannot clean them
> I will investigate further, but switching back to 6.6.0 solved the issue. 
> [Edit]
> The tests are run with TestNG and using 'mvn test'

--
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