jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: I've Put Some Jmeter Plugins Up on Github
Date Thu, 12 May 2011 11:00:20 GMT
On 12 May 2011 11:41, Adrian Speteanu <asp.adieu@gmail.com> wrote:
> On Wed, May 11, 2011 at 8:34 PM, Deepak Shetty <shettyd@gmail.com> wrote:
>
>> >JmeterThreadGlobal: Stores data from samplers into a java hash table, and
>> >provides a sampler to extract this data into an array at some later point.
>> >I've found this to be handy for communicating google widget tookit RPC
>> >strongnames to multiple threads.
>>
>> FYI you could do something similar using the BSH shared object - described
>> under http://jakarta.apache.org/jmeter/usermanual/best-practices.html -
>> Sharing variables  , though some sort of plugin will probably be easier
>> than
>> coding it
>>
>
> I missed that... of course this is the ultimate solution for more complex
> problems: writing your own class that you can use to keep track and share
> whatever you want. Has a major disadvantage - the test must end gracefully
> so you can properly destroy the memory used by this.
>

Note that the BSH elements support the ThreadListener and TestListener
interfaces, which can be used for closedown.

User-written elements can also implement the interfaces.

>>
>> regards
>> deepak
>>
>> On Wed, May 11, 2011 at 10:21 AM, Bruce Ide <flyingrhenquest@gmail.com
>> >wrote:
>>
>> > They do very similar things. To be honest, I missed the synchronizing
>> timer
>> > when I was looking around for info on doing this sort of thing.
>> >
>> > JmeterThreadSync does seem to have the slight advantage of being able to
>> > communicate across thread groups, making setup and teardown threads
>> > feasible. Once that functionality is implemented in jmeter, I won't be
>> > using
>> > JmeterThreadSync for anything Jmeter doesn't already do.
>> >
>> > I'll probably be stuck with it for a while, though. My policy is to not
>> use
>> > plugins that replicate jmeter functionality, but I'm stuck testing on
>> > jmeter
>> > 2.3.4 at the moment. I need a compelling reason to upgrade to 2.4., and
>> > working include controllers apparently isn't enough. Fortunately it
>> wasn't
>> > hard to back-port the 2.4 include controller to 2.3.4. I'll lobby for a
>> > jmeter upgrade again when setup and teardown threads go in.
>> >
>> > --
>> > Bruce Ide
>> > FlyingRhenquest@gmail.com
>> >
>>
>

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


Mime
View raw message