[
https://issues.apache.org/jira/browse/WICKET-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604059#action_12604059
]
Peter Ertl commented on WICKET-1693:
------------------------------------
If you want to run the test project to reproduce the bug.
un-tar-gz the project and open with IDEA 7 (didn't try with eclipse or IDEA?)
run TestLauncher.main()
open WorkBench.jmx in JMeter and press 'Start'
see NullPointerExceptions appearing in the log after a few seconds...
(at least it did on my macbook pro intel, mac os x 10.5.3, jvm 1.5)
> 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, test-project.tar.gz,
> WorkBench.jmx
>
>
> 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.
