Re: problem with remote beanshell configuration

2010-09-23 Thread Himanshu Ghai
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

Re: problem with remote beanshell configuration

2010-09-23 Thread sebb
On 23 September 2010 18:11, Himanshu Ghai himanshug...@gmail.com wrote: This is resolved..Thanks Sebb.. There is a related problem that I face now. Please start a new thread for a new problem. - To unsubscribe, e-mail:

problem with remote beanshell configuration

2010-08-31 Thread Himanshu Ghai
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

Re: problem with remote beanshell configuration

2010-08-31 Thread sebb
On 31 August 2010 18:30, Himanshu Ghai himanshug...@gmail.com 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

Re: problem with remote beanshell configuration

2010-08-31 Thread Himanshu Ghai
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 Other properties from jmeter.properties file are

Re: problem with remote beanshell configuration

2010-08-31 Thread sebb
On 31 August 2010 19:46, Himanshu Ghai himanshug...@gmail.com 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):

Re: problem with remote beanshell configuration

2010-08-31 Thread Himanshu Ghai
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

Re: problem with remote beanshell configuration

2010-08-31 Thread sebb
On 31 August 2010 21:11, Himanshu Ghai himanshug...@gmail.com 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

Re: problem with remote beanshell configuration

2010-08-31 Thread Himanshu Ghai
Thanks Sebb, is there a way that I can get it to execute when I run remotely.. On Tue, Aug 31, 2010 at 3:15 PM, sebb seb...@gmail.com wrote: On 31 August 2010 21:11, Himanshu Ghai himanshug...@gmail.com wrote: It executes on the controller machine when I launch jmeter with this command

Re: problem with remote beanshell configuration

2010-08-31 Thread sebb
On 31 August 2010 23:31, Himanshu Ghai himanshug...@gmail.com 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

Re: problem with remote beanshell configuration

2010-08-31 Thread Himanshu Ghai
will try it..thanks for quick responses On Tue, Aug 31, 2010 at 3:37 PM, sebb seb...@gmail.com wrote: On 31 August 2010 23:31, Himanshu Ghai himanshug...@gmail.com 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