You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Noel O'Brien <no...@newbay.com> on 2010/04/01 12:40:01 UTC
Debugging JMeter
Hi all,
Just a general question around debugging Beanshell scripts. Are there any useful tools/settings/whatever which can increase the verbosity of errors when there're error's with beanshell scripts? Usually the errors that appear in jmeter.log are as informative as "Could not eval source file", whereas it would be much more useful if it was possible to determine the lien number and type of error?
Any thoughts?
Regards,
Noel
Re: Debugging JMeter
Posted by Deepak Shetty <sh...@gmail.com>.
If your script is complex enough that you cant easily detect problems
visually then perhaps you can write it as a java class that can be called
from beanshell ? Its what I do after I get tired of adding print statements
after every line :).
regards
deepak
On Thu, Apr 1, 2010 at 3:40 AM, Noel O'Brien <no...@newbay.com> wrote:
> Hi all,
>
> Just a general question around debugging Beanshell scripts. Are there any
> useful tools/settings/whatever which can increase the verbosity of errors
> when there're error's with beanshell scripts? Usually the errors that appear
> in jmeter.log are as informative as "Could not eval source file", whereas it
> would be much more useful if it was possible to determine the lien number
> and type of error?
>
> Any thoughts?
>
> Regards,
> Noel
>
Re: Debugging JMeter
Posted by sv...@icarinae.com.
There is a Eclipse plugin for Beanshell too
http://eclipse-shell.sourceforge.net/
On Thu, 1 Apr 2010 15:59:27 +0100, sebb <se...@gmail.com> wrote:
> On 01/04/2010, Noel O'Brien <no...@newbay.com> wrote:
>> Thanks for the reply Sebb.
>>
>> Do all BSH languages suffer from the problem of returning
>> not-very-useful infto to JMeter?
>
> I think you may mean BSF.
>
> Sorry, I don't know.
>
>> FWIW, all my scripts are already in external files, but it doesn't
seem
>> to make any difference :(
>>
>> Regarding the "commenting out", I've been using print statement to
>> locate issues in scrtipts to date, but I'm looking for a more elegant
>> solution :)
>>
>> Looks like not much can be done about it then ;(
>>
>> Thanks for your help
>>
>> Regards,
>> Noel
>>
>>
>> ----- "sebb" <se...@gmail.com> wrote:
>> > On 01/04/2010, Noel O'Brien <no...@newbay.com> wrote:
>> > > Hi all,
>> > >
>> > > Just a general question around debugging Beanshell scripts. Are
>> > > there any useful tools/settings/whatever which can increase the
>> > > verbosity of errors when there're error's with beanshell scripts?
>> > > Usually the errors that appear in jmeter.log are as informative as
>> > > "Could not eval source file", whereas it would be much more useful
>> > > if it was possible to determine the lien number and type of error?
>> > >
>> >
>> > That's all that BeanShell tells JMeter.
>> >
>> > > Any thoughts?
>> >
>> > You could try:
>> >
>> > Put the script in a file, and you might get line numbers.
>> >
>> > Execute the script stand-alone in BeanShell.
>> >
>> > Comment out parts of the script until the error changes or goes
away.
>> >
>> > > Regards,
>> > >
>> > > Noel
>> > >
>> >
>>
>> > ---------------------------------------------------------------------
>> > 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
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Debugging JMeter
Posted by Noel O'Brien <no...@newbay.com>.
That's what I meant alright ;)
Regards,
Noel
----- "sebb" <se...@gmail.com> wrote:
> On 01/04/2010, Noel O'Brien <no...@newbay.com> wrote:
> > Thanks for the reply Sebb.
> >
> > Do all BSH languages suffer from the problem of returning not-very-useful infto to JMeter?
>
> I think you may mean BSF.
>
> Sorry, I don't know.
>
> > FWIW, all my scripts are already in external files, but it doesn't seem to make any difference :(
> >
> > Regarding the "commenting out", I've been using print statement to locate issues in scrtipts to date, but I'm looking for a more elegant solution :)
> >
> > Looks like not much can be done about it then ;(
> >
> > Thanks for your help
> >
> > Regards,
> > Noel
> >
> >
> > ----- "sebb" <se...@gmail.com> wrote:
> > > On 01/04/2010, Noel O'Brien <no...@newbay.com> wrote:
> > > > Hi all,
> > > >
> > > > Just a general question around debugging Beanshell scripts. Are there any useful tools/settings/whatever which can increase the verbosity of errors when there're error's with beanshell scripts? Usually the errors that appear in jmeter.log are as informative as "Could not eval source file", whereas it would be much more useful if it was possible to determine the lien number and type of error?
> > > >
> > >
> > > That's all that BeanShell tells JMeter.
> > >
> > > > Any thoughts?
> > >
> > > You could try:
> > >
> > > Put the script in a file, and you might get line numbers.
> > >
> > > Execute the script stand-alone in BeanShell.
> > >
> > > Comment out parts of the script until the error changes or goes away.
> > >
> > > > Regards,
> > > >
> > > > Noel
> > > >
> > >
> >
> > > ---------------------------------------------------------------------
> > > 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
>
>
Re: Debugging JMeter
Posted by sebb <se...@gmail.com>.
On 01/04/2010, Noel O'Brien <no...@newbay.com> wrote:
> Thanks for the reply Sebb.
>
> Do all BSH languages suffer from the problem of returning not-very-useful infto to JMeter?
I think you may mean BSF.
Sorry, I don't know.
> FWIW, all my scripts are already in external files, but it doesn't seem to make any difference :(
>
> Regarding the "commenting out", I've been using print statement to locate issues in scrtipts to date, but I'm looking for a more elegant solution :)
>
> Looks like not much can be done about it then ;(
>
> Thanks for your help
>
> Regards,
> Noel
>
>
> ----- "sebb" <se...@gmail.com> wrote:
> > On 01/04/2010, Noel O'Brien <no...@newbay.com> wrote:
> > > Hi all,
> > >
> > > Just a general question around debugging Beanshell scripts. Are there any useful tools/settings/whatever which can increase the verbosity of errors when there're error's with beanshell scripts? Usually the errors that appear in jmeter.log are as informative as "Could not eval source file", whereas it would be much more useful if it was possible to determine the lien number and type of error?
> > >
> >
> > That's all that BeanShell tells JMeter.
> >
> > > Any thoughts?
> >
> > You could try:
> >
> > Put the script in a file, and you might get line numbers.
> >
> > Execute the script stand-alone in BeanShell.
> >
> > Comment out parts of the script until the error changes or goes away.
> >
> > > Regards,
> > >
> > > Noel
> > >
> >
>
> > ---------------------------------------------------------------------
> > 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
Re: Debugging JMeter
Posted by Noel O'Brien <no...@newbay.com>.
Thanks for the reply Sebb.
Do all BSH languages suffer from the problem of returning not-very-useful infto to JMeter?
FWIW, all my scripts are already in external files, but it doesn't seem to make any difference :(
Regarding the "commenting out", I've been using print statement to locate issues in scrtipts to date, but I'm looking for a more elegant solution :)
Looks like not much can be done about it then ;(
Thanks for your help
Regards,
Noel
----- "sebb" <se...@gmail.com> wrote:
> On 01/04/2010, Noel O'Brien <no...@newbay.com> wrote:
> > Hi all,
> >
> > Just a general question around debugging Beanshell scripts. Are there any useful tools/settings/whatever which can increase the verbosity of errors when there're error's with beanshell scripts? Usually the errors that appear in jmeter.log are as informative as "Could not eval source file", whereas it would be much more useful if it was possible to determine the lien number and type of error?
> >
>
> That's all that BeanShell tells JMeter.
>
> > Any thoughts?
>
> You could try:
>
> Put the script in a file, and you might get line numbers.
>
> Execute the script stand-alone in BeanShell.
>
> Comment out parts of the script until the error changes or goes away.
>
> > Regards,
> >
> > Noel
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
Re: Debugging JMeter
Posted by sebb <se...@gmail.com>.
On 01/04/2010, Noel O'Brien <no...@newbay.com> wrote:
> Hi all,
>
> Just a general question around debugging Beanshell scripts. Are there any useful tools/settings/whatever which can increase the verbosity of errors when there're error's with beanshell scripts? Usually the errors that appear in jmeter.log are as informative as "Could not eval source file", whereas it would be much more useful if it was possible to determine the lien number and type of error?
>
That's all that BeanShell tells JMeter.
> Any thoughts?
You could try:
Put the script in a file, and you might get line numbers.
Execute the script stand-alone in BeanShell.
Comment out parts of the script until the error changes or goes away.
> Regards,
>
> Noel
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org