Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your option I think is to implement a <a href="http://jmeter.apache.org/usermanual/component_reference.html#Java_Request" rel="nofollow">Java Request Sampler</a>. </p> <p>You could define the following parameters for your <a href="http://jmeter.apache.org/api/org/apache/jmeter/protocol/java/sampler/JavaSamplerClient.html" rel="nofollow">Java Request Sampler</a> implementation:</p> <ul> <li>server host </li> <li>server port </li> <li>connection identifier(see later)</li> <li>session identifier</li> <li>data</li> </ul> <p>Read carefully the documentation of <a href="http://jmeter.apache.org/api/org/apache/jmeter/protocol/java/sampler/JavaSamplerClient.html" rel="nofollow">JavaSamplerClient</a> to understand the lifecycle. Each thread will have one instance of your sampler.</p> <p>Then in your implementation you need to take care of the following things:</p> <ul> <li>create a connection handler class, which opens up sockets for each connection identifier. Test cases using the same connection identifier will send data through the same socket. This connection handler should take care of sending the data synchronized way and to give back the response to the appropiate instance, which is waiting for it</li> <li>in your sampler you have to create exactly one connection handler (or one per server, or one per port, as you wish)</li> <li>when the sampler sends some text, you give it to the connection handler, and the sampler waits till the response comes. </li> </ul> <p>This way you can simply convert your asynchronous problem to a synchronous one with implementing this conenction handler, which is shared between the sampler instances. But take care of the implementation to be sure that your thread programming does not fake the results with some testing tool side bottleneck.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload