Sandhya,
Can I have the full logs from one of the JMeter servers and the
controller (maybe through pastebin.com) after you've made the changes
described below. I'm struggling to think as to why it would matter what
test plan you're running. Maybe someone else on the list will have
insight into
Thanks for response. I think I can get the expected result by changing
Thread Group properties with formula: (Number of Threads * Loop Count) /
Expected delay between threads = Ramp-up period. But is it possible to
achieve the same result without modifying thread group properties, i.e. to
force
Hi Jeff,
Thanks for the information.
I had missed to place the CSV data file (parameterized users) in Slaves and
provide the file path in Jmeter Master. When placed the file and executed the
script, the script is executed and provides the expected output.
However, the error message still
On 7 August 2014 09:32, Sandhya Kiran sandhya.ki...@mimos.my wrote:
Hi Jeff,
Thanks for the information.
I had missed to place the CSV data file (parameterized users) in Slaves and
provide the file path in Jmeter Master. When placed the file and executed the
script, the script is executed
On 25 July 2014 20:30, Doug Breaux doug.bre...@gmail.com wrote:
I've updated my PATH to include keytool:
https://wiki.apache.org/jmeter/TestRecording210
I've deleted the proxyserver.jks file:
On Thu, 2014-08-07 at 14:39 +0100, sebb wrote:
On 7 August 2014 09:32, Sandhya Kiran sandhya.ki...@mimos.my wrote:
Hi Jeff,
Thanks for the information.
I had missed to place the CSV data file (parameterized users) in Slaves and
provide the file path in Jmeter Master. When placed the
Hi,
It actually gets worse than that. The looping behavior means that tx will be
throttled by your servers ability to process requests. The throughput shaping
timer is good for slowing things down to a particular tx rate but it cannot
correct for back pressure from the server. The only way to
