cvs commit: jakarta-jmeter/lib ant-1.5-optional.jar ant-1.5.jar ant-1.4.1.jar jakarta-ant-1.4.1-optional.jar

mstover12002/08/12 12:14:08 Modified:.build.xml Added: lib ant-1.5-optional.jar ant-1.5.jar Removed: lib ant-1.4.1.jar jakarta-ant-1.4.1-optional.jar Log: Fixing generation of api-docs using Ant build file. Upgrading to Ant 1.5 Revision Change

cvs commit: jakarta-jmeter/src/protocol/http/org/apache/jmeter/protocol/http/sampler HTTPSampler.java HTTPSamplerFull.java

mstover12002/08/12 11:12:37 Modified:src/core/org/apache/jmeter/resources messages_de.properties src/protocol/http/org/apache/jmeter/protocol/http/sampler HTTPSampler.java HTTPSamplerFull.java Log: Fixing bug 11639 (saving follow redirects attr

DO NOT REPLY [Bug 11639] - save Follow Redirect in a .jmx file

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 11639] New: - save Follow Redirect in a .jmx file

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

Re: BUG 11536 - throughput calculation

Bytes/time could easily be accomodated, and I see no reason not to. However, there's a larger issue, I think, having to do with how the measurement is made. Currently, the throughput measurement measures how many requests are finished from the start of the test run till the end. This means

Re: view results tree -> http request

Sorry I didn't read all of my inbox before kicking in. Mike is so amazingly fast... Salut, Jordi. Jordi Salvat i Alabart wrote: > This is a bug. I've just hit the same thing: http samplers in a single > Simple Controller keep accumulating parameters from the previous ones. > > A quick workar

Re: BUG 11536 - throughput calculation

In my experience, requests per unit of time is a more important value than bytes per unit of time when load testing web applications. The former usually relates to CPU power used (there isn't much difference between spitting out 1K or 2K of data) -- and CPU is most often the bottleneck in this

Re: view results tree -> http request

This is a bug. I've just hit the same thing: http samplers in a single Simple Controller keep accumulating parameters from the previous ones. A quick workaround is to put each HTTP Sampler in its own Simple Controller. Painful, but it works. Salut, Jordi. P.S. I have no time to report this p

Re: BUG 11536 - throughput calculation

I think my understanding of throughput is different. When I look at the throughput number, it is telling me how many requests the server is handling per unit time (in this case, # requests/minute). That's what I want to know. I see no way of accurately reporting that info other than the wa

DO NOT REPLY [Bug 11634] New: - Option to select the language

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

BUG 11536 - throughput calculation

Hi, I have looked at the code and at the output of the GraphVisualizer and GraphModel and I am amazed. I never thought much about it since it hasn't been of much interest up to now. But I thought it would calculate the amount of bytes per time. Yet by looking at the code I realize it calculates t

cvs commit: jakarta-jmeter/xdocs/usermanual get-started.xml

mstover12002/08/12 06:26:28 Modified:docs running.html docs/usermanual get-started.html xdocs/usermanual get-started.xml Log: Doc note about problems with JDK1.4.1-beta Revision ChangesPath 1.51 +0 -0 jakarta-jmeter/docs/runnin

Re: view results tree -> http request

It is fixed. This was a new, old bug. The bad behavior was always there, but it was cancelled out by other bad behavior, which I very recently fixed. Now, both have been changed to good behavior. Behavioral programming is the way of the future! -Mike On 12 Aug 2002 at 8:51, Mike Stover wrote

cvs commit: jakarta-jmeter/src/core/org/apache/jmeter/threads TestCompiler.java

mstover12002/08/12 06:18:10 Modified:src/components/org/apache/jmeter/visualizers AssertionVisualizer.java src/core/org/apache/jmeter/threads TestCompiler.java Log: Assertion visualizer shows sampler data Preventing samplers from interfering

Re: view results tree -> http request

Looks like a bug. I'm checking it out now. -Mike On 12 Aug 2002 at 11:48, Stiepel, Jochen wrote: > Hello, > > a very simple thing. > > -Thread group > -HTTP Request Defaults > -HTTP Cookie Manager > -HTTP Request A (Parameter Name: xmlrequest ; Value: > 1234) > -HTTP Re

view results tree -> http request

Hello, a very simple thing. -Thread group -HTTP Request Defaults -HTTP Cookie Manager -HTTP Request A (Parameter Name: xmlrequest ; Value: 1234) -HTTP Request B (Parameter Name: xmlrequest ; Value: 7890) -View Results Tree so and if I go to the "View Res