Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of sebbaz@gmail.com designates
 64.233.182.196 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=AzWIluZOHJy9pBDmwFNmF/0utlRkcd8DsUjxAmRxb86JqqARTdxXXMYGqr4to/ZcLsb1nTIrvKcqqTCyRsJcH+L5ED+b8GoVFmiI3r0ZDuupWutjijM8RfkGBIKPg0g/hZ2XN2ghG0hrjJ+GSq53o6/fqX7UFy2HqC3r62EeTtc=
Message-ID: <25aac9fc05070105113a2e46e3@mail.gmail.com>
Date: Fri, 1 Jul 2005 13:11:02 +0100
From: sebb <sebbaz@gmail.com>
Reply-To: sebb <sebbaz@gmail.com>
To: Rabi Lahiri <rabi.lahiri@gmail.com>
Subject: Re: HTTP timeouts with __StringFromFile function
Cc: JMeter Users List <jmeter-user@jakarta.apache.org>
In-Reply-To: <3da8afd605063018117fc05a2f@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <3da8afd605062916097fcdb3c6@mail.gmail.com>
	 <25aac9fc050630024936c17b60@mail.gmail.com>
	 <3da8afd605063018117fc05a2f@mail.gmail.com>

Which version of Jmeter are you using?

I don't understand what's happening here.

Try replacing your HTTP Sampler with a JavaTest sampler to see if the
timings are affected by the presence of the user parameter
pre-processor or not.

Or indeed try using the standard HTTP Sampler instead of yours.

If either of these shows the timing problem, please create a Bugzilla
issue, and then attach the following:

- simple test script that has OK timing data
- simple test script that causes timing data problems
- jmeter.log for both test runs
- jtl files for both runs.

S.

P.S. If you thing the changes you made to the HTTP Sampler might be
useful to others, perhaps you would consider filing a Bugzilla
enhancement request to describe what you have added.

On 7/1/05, Rabi Lahiri <rabi.lahiri@gmail.com> wrote:
> I have the duration assertion as a child of the sampler.
>=20
> Something interesting I noticed just now, though - if I use static
> arguments and no User parameter preprocessor with the sampler, the
> timing data looks fine.  If I add the user parameter preprocessor with
> two $_StringFromFile functions (as a child of the sampler), the timing
> data gets messed up and looks cumulative among all the threads, even
> if I don't actually use the variables from the file (i.e. I leave the
> arguments to the sampler as static data).
>=20
> Could the thread timers be including the time that each thread is
> blocked on I/O or somehow accumulating time because of that?  We have
> subclassed the HTTPSampler and AbstractSamplerGui for our project;
> otherwise everything is from the standard distribution.
>=20
> thanks again,
> Rabi
>=20
> On 6/30/05, sebb <sebbaz@gmail.com> wrote:
> > Where have you put the duration assertions in relation to the samplers?
> >
> > Which version of JMeter are you using?
> >
> > S
> > On 6/30/05, Rabi Lahiri <rabi.lahiri@gmail.com> wrote:
> > > Hi,
> > > I've looked through all the docs I could find and the mail archives
> > > and couldn't find an answer to this.  I have a subclass of HTTPSample=
r
> > > and need to implement timeouts for my requests.  I'm using the sample=
r
> > > with the following setup:
> > >
> > > 500 threads
> > > 1 loop
> > > parameter "args" is _StringFromFile(args.txt)
> > > parameter "method" is _StringFromFile(methods.txt)
> > >
> > > My service needs to pass args and method dynamically this way.
> > > args.txt and methods.txt are 500-line files which constitute the
> > > requests I need.  This works fine and I can test the results of each
> > > with response assertions, except that duration assertions don't work
> > > properly.  The duration assertion appears to be timing the whole set
> > > of 500 threads instead of each one individually, so as soon as the
> > > group time hits the assertion value every thread fails.  For example,
> > > let's say each call takes exactly 200 ms.  If I set the duration
> > > assertion to 1100ms, the first five responses succeed but all the res=
t
> > > fail.  I need to be able to set it up so that I can verify that no
> > > individual call takes more than, say, 250ms.  Is this possible?  If I
> > > need to make a code change, can it be done relatively simply?
> > >
> > > thanks,
> > > Rabi Lahiri
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> > >
> > >
> >
>

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