Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362511 - Contribution of stress test for Server
Summary: Contribution of stress test for Server
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Server-Side (show other bugs)
Version: 3.8.0 Juno   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Simon Archer CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-31 12:39 EDT by Chris Goldthorpe CLA
Modified: 2019-10-14 00:25 EDT (History)
1 user (show)

See Also:


Attachments
Test plug-in (10.85 KB, application/zip)
2011-10-31 12:44 EDT, Chris Goldthorpe CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Goldthorpe CLA 2011-10-31 12:39:11 EDT
One of the tests in the User Assistance Test Suite, ParallelServerAccessTest is actually a stress test for the server and logically belongs in the Equinox test suite. The test starts up a server and has a number of threads trying to simultaneously access the server. This test periodically fails about once a month in the nightly builds and I believe that on those occasions it is triggering a race condition. I have never been able to figure out exactly what is happening, but I think that we should be running this test against Jetty 8.

The UA test suite just contained testServletReadInParallel(), I have added two variants of the test which run 10 and 100 times longer, which greatly increase the chance of failure. I will attach a bundle containing the test.
Comment 1 Chris Goldthorpe CLA 2011-10-31 12:44:40 EDT
Created attachment 206225 [details]
Test plug-in
Comment 2 Thomas Watson CLA 2011-10-31 13:11:09 EDT
Thanks Chris!

Simon A. could you have a look.
Comment 3 Eclipse Genie CLA 2019-10-14 00:25:49 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.