DO NOT REPLY [Bug 42267] - Concurrent GUI update failure

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42267>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42267





------- Additional Comments From alf@i100.no  2007-05-02 05:52 -------
Created an attachment (id=20088)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=20088&action=view)
Suggested patch

The patch makes the deliverSampler method synchronized.
Since the Proxy starts one thread for each request it receives, and each thread
adds a sample to the test plan via the "ProxyControl.deliverSampler" method,
the method has to be synchronized. The "deliverSampler" method interacts with
GUI components, which are normally run on the GUI thread, i.e. just one thread.
Therefore, only one thread at the time should be able to deliver samples.
The org.apache.jmeter.gui.GuiPackage class for example, does not seem to be
threadsafe, and methods in that class is called indirectly by deliverSampler.

You can reproduce this bug by pointing your browser to a web site with many
images on the page, so that the browsers issues multiple concurrent requests.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org