On 29/09/2009, Bob Yetman <[email protected]> wrote: > I've starting working on adding Interruptible to SubscriberSampler.java, no > problems there, simple 3 line function for now. > However, the Thread group that the JMS Subscriber is called from never ends > when you try and interrupt the test. > > The log looks something like this: > > INFO - jmeter.gui.action.start: Stopping test > INFO - jmeter.threads.JMeterThread: Stopping my thread > WARN - jmeter.threads.JMeterThread: Interrupting: my thread sampler: JMS > Subscriber > DEBUG- jmeter.protocol.jms.sampler.SubscriberSampler: > SubscriberSampler.interrupt called ** my new method ** > INFO - jmeter.protocol.jms.client.OnMessageSubscriber: > Subscriber closed ** called from my new method ** > DEBUG - jmter.protocol.jms.sampler.SubscriberSampler: > sleep interrupted > WARN - jmeter.engine.StandardJMeterEngine: Thread won't > exit: my thread
You have not shown the times from the log - these are important in determining whether or not the engine sees the thread completion. If it takes too long for the sampler to finish, the engine complains. > The best I can figure is that in JMeterThread.java, the stop() method is > called when the test is interrupted, but the stop() > method doesn't do anything to actually shut down the thread, unlike the > threadFinished() method, which is called when a > thread ends normally. > > Am I reading the code right? Or am I missing something in the threading > code that is called when attempting to terminate a > thread? > > Bob Yetman > > --------------------------------------------------------------------- > 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]
