On 07/01/2008, Dan <[EMAIL PROTECTED]> wrote: > This is using the ant jmeter task. > > All the settings which define e.g. number of threads are defined as part of > the ant task. So does that mean they should get passed over?
Properties defined using -J and -D are only defined in the local JMeter. This is true for all invocation methods. Only the new -G option allows properties to be sent to the server. > Network congestion isnt a problem for me at this time - i'm doing very high > numbers of tiny requests. Which will generate very high numbers of request responses all of which are funnelled back to the client - unless you don't use any listeners. > I'll try JMeter 2.3.1 and see if it makes any difference, but if there's any > other way i can debug or analyse this problem then please let me know! This is the first version that supports the -G option. > (I'll also check the version of my ant task, maybe thats old?) Perhaps, but AFAIK, it has not been updated for 2.3.1 I think you'll need to use Ant + <java> or shell scripts. > Rgds, > Dan > > --------- Original Message -------- > From: sebb <[EMAIL PROTECTED]> > To: JMeter Users List <[email protected]>, Dan > <[EMAIL PROTECTED]> > Subject: Re: Running Remote, via ANT > Date: 06/01/08 22:24 > > > On 04/01/2008, Dan <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > We run our JMeter scripts via ant, and pass in various values which > are used > > > to define the number of threads for each threadgroup to use, etc. > > > > Are you using pure Ant, or the Ant JMeter task? > > > > > Due to a problem where we're seeing irregular arrival rates we want > to try > > > spreading the load across multiple servers. So I setup and executed > > > jmeter-server on the localhost box, and a remote box. This works > fine, and > > > the rmiregistry and server seem to start ok. > > > > Controlling more than a few servers from one client can cause network > > congestion and/or resource exhaustion at the client, as all the > > responses are funnelled back to the client. > > > > > I then execute my tests from the ant scripts in the usual way, > telling it to > > > use localhost and the remote servers. They connect up ok, and seem > to start > > > the testplan however all the messages show "Starting 0 threads > for group". > > > > Server or client? > > > > Are you using a property or variable to define the number of threads? > > If it's not defined, then JMeter could interpret that as zero. > > > > > FWIW the location of the harness, vm, jmeter, testplans etc is the > same on > > > both machines. > > > > > > So what I dont understand is how should the various parameters that I > pass > > > to jmeter be then passed to the remote boxes? > > > > JMeter 2.3.1 added the ability to pass properties to remote servers > > using the -G command-line flag. However that is not supported via the > > ant-jmeter jar (yet). But you can pass whatever flags you like using > > Ant with the <arg> tag. > > > > > This is all headless as well - due to the number of parameters we set > via > > > ant it's not possible to run up a gui client with those values set. > > > > Non-GUI uses fewer resources, especially in 2.3.1. > > > > > Thanks, > > > Dan > > > > > > ________________________________________________ > > > Message sent using UebiMiau 2.7.10 > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > ________________________________________________ > Message sent using UebiMiau 2.7.10 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
