On 07/01/2009, Thomas Johnson <[email protected]> wrote: > Hm, that's quite strange. You might want to file a bug report about > this -- I'm not sure if that behavior is intentional or not. A quick > scan of the docs doesn't say anything about an init or teardown call > for postprocessors.
From http://jakarta.apache.org/jmeter/usermanual/component_reference.html#BeanShell_PostProcessor The BSH P-P "... supports the ThreadListener and TestListener methods. These should be defined in the initialisation file. See the file BeanShellListeners.bshrc for example definitions. " However, the methods are only called if you define them, so I agree it's strange, and I don't see the same problem. > In the meantime, do the extra runs cause a problem for you? > > > On Wed, Jan 7, 2009 at 10:27 AM, Laurent Michenaud <[email protected]> > wrote: > > Yes, the bsh postprocessor is a child of the http sampler. > > > > I have just put an beanShell postprocessor with a log command (hello) and > > here what i can see in the log file : > > > > 2009/01/07 10:25:01 INFO - jmeter.engine.StandardJMeterEngine: Running the > > test! > > 2009/01/07 10:25:01 INFO - jmeter.functions.LogFunction: Thread-493 : > hello > > > > 2009/01/07 10:25:01 INFO - jmeter.gui.util.JMeterMenuBar: > > setRunning(true,*local*) > > 2009/01/07 10:25:02 INFO - jmeter.engine.StandardJMeterEngine: Starting 1 > > threads for group Groupe de thread. Ramp up = 0. > > 2009/01/07 10:25:02 INFO - jmeter.engine.StandardJMeterEngine: Thread will > > stop on error > > 2009/01/07 10:25:02 INFO - jmeter.threads.JMeterThread: Thread Groupe de > > thread 1-1 started > > 2009/01/07 10:25:02 INFO - jmeter.services.FileServer: Stored: > > /********************/users.txt > > 2009/01/07 10:25:02 INFO - jmeter.functions.LogFunction: Groupe de thread > > 1-1 : hello > > 2009/01/07 10:25:02 INFO - jmeter.threads.JMeterThread: Thread Groupe de > > thread 1-1 is done > > 2009/01/07 10:25:02 INFO - jmeter.engine.StandardJMeterEngine: Ending > > thread Groupe de thread 1-1 > > 2009/01/07 10:25:02 INFO - jmeter.engine.StandardJMeterEngine: Stopping > > test > > 2009/01/07 10:25:02 INFO - jmeter.engine.StandardJMeterEngine: Notifying > > test listeners of end of test > > 2009/01/07 10:25:02 INFO - jmeter.services.FileServer: Close: > > /********************/users.txt > > 2009/01/07 10:25:02 INFO - jmeter.functions.LogFunction: Thread-495 : > hello > > > > 2009/01/07 10:25:02 INFO - jmeter.gui.util.JMeterMenuBar: > > setRunning(false,*local*) > > 2009/01/07 10:25:02 INFO - jmeter.engine.StandardJMeterEngine: Test has > > ended > > > > I don't know what is Thread-493 and Thread-495 > > > > 2009/1/7 Thomas Johnson <[email protected]> > > > >> Just to double-check, is your Test Plan structured as follows? > >> Thread Group > >> - HTTP Sampler (page 1) > >> - HTTP Sampler (page 2) > >> -- BSH Postprocessor > >> > >> The Postprocessor needs to be a child of the sampler. If not, it might > >> be picking up the other Samplers in your test plan as well. > >> > >> On Wed, Jan 7, 2009 at 9:32 AM, Laurent Michenaud <[email protected]> > >> wrote: > >> > Hi, > >> > > >> > I have added a bsh post processor on a single httpd request node. > >> > The post processor is executed three times and i don't understand > >> > why. Only one thread is configured and only one loop. > >> > > >> > It is like there is a kind of init, the loop execution(thread group), > and > >> > then the release. > >> > It is a problem for me as my bsh script fails on the init/release phase. > >> > It works well on the loop execution. > >> > > >> > Thanks for your response. > >> > Laurent > >> > > >> > >> --------------------------------------------------------------------- > >> 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]
