Re: Accessing StandardJMeterEngine.allThreads

sebb <[email protected]>
Newsgroups gmane.comp.jakarta.cactus.devel
Message-ID <CAOGo0Vb3pQcX1=uV-n61AooZXUuOQs0F47ZJADwiiCsYmyQ3nQ@mail.gmail.com>
On 13 August 2011 13:13, Andrey Pohilko <[email protected]> wrote:
> Hi all!
>
> JMeter users frequently ask for some inter-thread communications on JMeter
> forums.

JMeter threads represent independent users; it should not be necessary
to pass data between them.

JMeter 2.5 will support setUp threads, which solve many of the use
cases I have seen.

> I have an idea of custom function that would give information from any
> thread for another thread. I think this will give wanted interaction.

I'd like to see some use cases that truly require cross-thread
communication before considering this.
The danger is that the interaction between the threads will cause
unnecessary locking.

> The problem implementing it is that only place where all JMeterThreads stored
> is StandardJMeterEngine.allThreads and I found no way to access that list.
>
> Field declaration from StandardJMeterEngine:
>        /** JMeterThread => its JVM thread */
>        private final Map<JMeterThread, Thread> allThreads;
>
>  So my questions are:
> 1. Is it possible to get access to that map in some read-only way (not to
> break anything...)?
> 2. If yes, how better do it: simple getter, or something more required? I'm
> ready to create and submit a patch to Bugzilla.
> 3. If the way is simple enough, could it be the part of JMeter 2.5 release,
> because waiting another year for the next release is obviously undesirable?
>
> Sorry, if I'm asking for too much, but with my efforts, too, JMeter becoming
> more and more popular load testing tool.
>
> Thank you!
> --
> Andrey Pohilko
> JP@GC Maintainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.