[
https://issues.apache.org/jira/browse/WICKET-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Compagner closed WICKET-1693.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.3.5
1.4-RC1
seems that it is already fixed i can run the test for quite some times without
any problems
> 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
> Affects Versions: 1.3.4, 1.4-M3
> 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
> Fix For: 1.4-RC1, 1.3.5
>
> Attachments: stacktrace-stress-test.txt,
> test-project-for-wicket-1.3.tar.gz, 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.
