You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Peter Ertl (JIRA)" <ji...@apache.org> on 2008/06/10 21:07:45 UTC
[jira] Created: (WICKET-1693) concurrency issue / race condition in
current wicket (will sometimes fail under stress)
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
Priority: Critical
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.
[jira] Updated: (WICKET-1693) concurrency issue / race condition in
current wicket (will sometimes fail under stress)
Posted by "Peter Ertl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl updated WICKET-1693:
-------------------------------
Attachment: stacktrace-stress-test.txt
> 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
> 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.
[jira] Closed: (WICKET-1693) concurrency issue / race condition in
current wicket (will sometimes fail under stress)
Posted by "Johan Compagner (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (WICKET-1693) concurrency issue / race condition
in current wicket (will sometimes fail under stress)
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (WICKET-1693) concurrency issue / race condition in
current wicket (will sometimes fail under stress)
Posted by "Peter Ertl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl updated WICKET-1693:
-------------------------------
Affects Version/s: 1.4-M3
1.3.4
> 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
> 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.
[jira] Updated: (WICKET-1693) concurrency issue / race condition in
current wicket (will sometimes fail under stress)
Posted by "Peter Ertl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl updated WICKET-1693:
-------------------------------
Attachment: WorkBench.jmx
test-project.tar.gz
uploaded my sample project + jmeter config file to reproduce the error
> 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.
[jira] Commented: (WICKET-1693) concurrency issue / race condition
in current wicket (will sometimes fail under stress)
Posted by "Matej Knopp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604019#action_12604019 ]
Matej Knopp commented on WICKET-1693:
-------------------------------------
That's weird, could you provide the URLs you are hitting? Do you e.g. create page with bookmarkable url and then hit it again with listener interface or is it something else? Looks like there might be problem with our locking being too relaxed.
> 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
> 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.
[jira] Updated: (WICKET-1693) concurrency issue / race condition in
current wicket (will sometimes fail under stress)
Posted by "Peter Ertl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl updated WICKET-1693:
-------------------------------
Attachment: test-project-for-wicket-1.3.tar.gz
upload the test project again without generics to test wicket-1.3 (current) with it. Unfortunately this issue seems to affect 1.3 _and_ 1.4.
> 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-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.
[jira] Commented: (WICKET-1693) concurrency issue / race condition
in current wicket (will sometimes fail under stress)
Posted by "Peter Ertl (JIRA)" <ji...@apache.org>.
[ 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.