Is there any concept of locks or semaphores in Jmeter? I am currently testing a web based API which accesses an internal database. I do a call to the API via the http request sampler. I then do another API call to verify that the correct thing happens. This works great with a single thread. However, when I go multi-threaded I get random failures. I am guessing that multiple threads are changing the same record in the database at the same time. Is there anyway to make 2 web requests an exclusive operation? This would seem to me to be a common problem with a multi-threaded stress tool. I've looked through the manual and can not find any type of locking mechanism. Otherwise does anyone having any ideas on how to simulate one? I'm thinking maybe just setting a global jmeter variable and then checking it's value before doing anything with the database. However, I don't think this would work running jmeter across multiple platforms. --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Garry,
if mechanism like locks or semaphores are desired, they should be implemented within the tested application.
JMeter merely simulates USING the application. It won't supply you with extra security mechanism not designed/not implemented in the tested application.
Best regards / Viele Grüße
Noam Paz
"Garry L. Thompson" <gt...@attensa.com>
27.02.2006 20:09 To
"JMeter Users List" <jm...@jakarta.apache.org>
cc
Please respond to
"JMeter Users List" <jm...@jakarta.apache.org> Subject
Locks or semaphores in Jmeter?
Is there any concept of locks or semaphores in Jmeter? I am currently testing
a web based API which accesses an internal database. I do a call to the API
via the http request sampler. I then do another API call to verify that the
correct thing happens. This works great with a single thread. However, when I
go multi-threaded I get random failures. I am guessing that multiple threads
are changing the same record in the database at the same time.
Is there anyway to make 2 web requests an exclusive operation? This would seem
to me to be a common problem with a multi-threaded stress tool. I've looked
through the manual and can not find any type of locking mechanism. Otherwise
does anyone having any ideas on how to simulate one? I'm thinking maybe just
setting a global jmeter variable and then checking it's value before doing
anything with the database. However, I don't think this would work running
jmeter across multiple platforms.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
--
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org