I dug around a bit more with OptimizeIt and verified that Orion's implementation does indeed create 2 threads for the RMI initialcontextfactory.
tomorrow I hope to finish implementing the two remaining features and then commit the code to CVS. I've decided to go with the Consumer.recieve() approach, since I can reliably clean up the subscriber and make sure the threads are destroyed. Although onMessage approach works, it means the stability of JMeter and the JMS sampler would be more vulnerable to bugs in JMS implementations. Whether the sampler uses onMessage(message) or recieve() results in the same number of threads created during runtime, so I'm going with the more reliable approach, even if onMessage(message) is recommended for async messages. peter --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
