This is resolved..Thanks Sebb.. There is a related problem that I face now..The http server started with beanshell.server.port=9000 does not start when I execute the tests remotely. I tried giving this property on command line as -Jbeanshell.server.port=9000 but didn't help.
On Tue, Aug 31, 2010 at 4:48 PM, Himanshu Ghai <[email protected]>wrote: > will try it..thanks for quick responses > > > On Tue, Aug 31, 2010 at 3:37 PM, sebb <[email protected]> wrote: > >> On 31 August 2010 23:31, Himanshu Ghai <[email protected]> wrote: >> > Thanks Sebb, is there a way that I can get it to execute when I run >> > remotely.. >> >> No. >> >> It is a startup script, it runs when you start JMeter, not when you >> start a test. >> >> However you can use a BeanShell test element wherever you like in the test >> plan. >> >> > >> > On Tue, Aug 31, 2010 at 3:15 PM, sebb <[email protected]> wrote: >> > >> >> On 31 August 2010 21:11, Himanshu Ghai <[email protected]> wrote: >> >> > It executes on the controller machine when I launch jmeter with this >> >> command >> >> > >> >> > ./jmeter -t plan_xxx.jmx -r >> >> > >> >> > then I run it on the configured remote hosts using menu option..it >> >> doesn't >> >> > execute there >> >> > on the remote hosts. one thing i noticed is that this code(.bsh) gets >> >> > executed not when >> >> > i run the test plan but when I launch jmeter... >> >> >> >> Yes, that is what is supposed to happen - it is a startup script. >> >> >> >> > by listener i meant our custom code that looks for incoming requests >> run >> >> by >> >> > the >> >> > .bsh file.. >> >> > >> >> > Himanshu >> >> > >> >> > On Tue, Aug 31, 2010 at 11:55 AM, sebb <[email protected]> wrote: >> >> > >> >> >> On 31 August 2010 19:46, Himanshu Ghai <[email protected]> >> wrote: >> >> >> > yes Sebb, jmeter controller machine and host servers have same >> >> >> > jmeter.properties >> >> >> > file. >> >> >> > >> >> >> > this line server initialization launches our custom code in >> >> startup.bsh >> >> >> that >> >> >> > starts a >> >> >> > listener (our modification): >> >> >> > >> >> >> > beanshell.server.file=../extras/startup.bsh >> >> >> >> >> >> So does the startup.bsh file gete executed or not? >> >> >> >> >> >> Note that listeners are treated specially by the JMeter >> client-server >> >> >> code - the test plan is actually changed on the fly when sending >> >> >> listeners to the server. >> >> >> This is necessary to ensure that the server listener code can send >> the >> >> >> sample data back to the client. >> >> >> >> >> >> > Other properties from jmeter.properties file are picked alright.. >> >> >> > >> >> >> > Many thanks for looking into this >> >> >> > >> >> >> > Himanshu >> >> >> > >> >> >> > >> >> >> > >> >> >> > On Tue, Aug 31, 2010 at 11:03 AM, sebb <[email protected]> wrote: >> >> >> > >> >> >> >> On 31 August 2010 18:30, Himanshu Ghai <[email protected]> >> >> wrote: >> >> >> >> > Greetings Jmeter users, >> >> >> >> > >> >> >> >> > In the jmeter.properties file under beanshell configuration we >> >> >> included a >> >> >> >> > modified startup.bsh file. Also changed the init >> >> >> >> > configuration. Everything works alright as expected if we >> launch >> >> the >> >> >> test >> >> >> >> > locally. However when we start the test from >> >> >> >> > a remote machine, the server initialization file under >> beanshell >> >> >> >> > configuration isn't executed. >> >> >> >> >> >> >> >> Did you update the server's copy of jmeter.properties file? >> >> >> >> >> >> >> >> > I have been struggling with it for a while..any help is >> >> appreciated.. >> >> >> >> > >> >> >> >> > Thanks >> >> >> >> > Himanshu >> >> >> >> > >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> >> 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] >> >> >> >> >> >> >> >> > >> >> >> >> --------------------------------------------------------------------- >> >> 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] >> >> >
