| java.lang.Object org.apache.jmeter.protocol.jms.client.ClientPool
ClientPool | public class ClientPool (Code) | | author: pete author: ClientPool holds the client instances in an ArrayList. The main purpose of author: this is to make it easier to clean up all the instances at the end of a test. author: If we didn't do this, threads might become zombie. |
addClient | public static void addClient(ReceiveSubscriber client)(Code) | | Add a ReceiveClient to the ClientPool. This is so that we can make sure
to close all clients and make sure all threads are destroyed.
Parameters: client - |
addClient | public static void addClient(OnMessageSubscriber client)(Code) | | Add a OnMessageClient to the ClientPool. This is so that we can make sure
to close all clients and make sure all threads are destroyed.
Parameters: client - |
addClient | public static void addClient(Publisher client)(Code) | | Add a Publisher to the ClientPool. This is so that we can make sure to
close all clients and make sure all threads are destroyed.
Parameters: client - |
clearClient | public static void clearClient()(Code) | | Clear all the clients created by either Publish or Subscribe sampler. We
need to do this to make sure all the threads creatd during the test are
destroyed and cleaned up. In some cases, the client provided by the
manufacturer of the JMS server may have bugs and some threads may become
zombie. In those cases, it is not the responsibility of JMeter for those
bugs.
|
|
|