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

Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2008/06/10 22:23:45 UTC

[jira] Assigned: (WICKET-1693) concurrency issue / race condition in current wicket (will sometimes fail under stress)

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

Igor Vaynberg reassigned WICKET-1693:
-------------------------------------

    Assignee: Johan Compagner

> concurrency issue / race condition in current wicket (will sometimes fail under stress)
> ---------------------------------------------------------------------------------------
>
>                 Key: WICKET-1693
>                 URL: https://issues.apache.org/jira/browse/WICKET-1693
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>         Environment: jetty 6.1.9, mac os x 10.5.3, jdk 1.5, wicket 1.4.x trunk (#665751)
>            Reporter: Peter Ertl
>            Assignee: Johan Compagner
>            Priority: Critical
>         Attachments: stacktrace-stress-test.txt
>
>
> In current wicket there seems to be a concurrency issue / race condition.
> I did some stress test with JMeter on my very simple wicket app with a very simple stateful page (mostly to determine render performance of wicket in pages/sec). The test was done with approximately 200-500 concurrent threads.
> After running for a few seconds NullPointerExceptions were appearing in the console log.
> I uploaded the log which contains quite a few stacktraces.

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