Java request in distributed testing

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Java request in distributed testing

1336230737-2
hello.
 i found  that  the established  TCP connection won't Disconnect after used Java Request test in distributed testing
Reply | Threaded
Open this post in threaded view
|

Re: Java request in distributed testing

glinius@live.com
If you're talking about *Java* implementation of the  HTTP Request
<https://jmeter.apache.org/usermanual/component_reference.html#HTTP_Request>  
sampler, according to the documentation:

<blockquote>
The Java HTTP implementation has some limitations:

There is no control over how connections are re-used. When a connection is
released by JMeter, it may or may not be re-used by the same thread.

</blockquote>

So if you're suffering from the above issue you should consider switching to
the  HttpClient4 <https://hc.apache.org/>  implementation

If you're seeing Connection header with the value of *keep-alive* - just
untick "Use KeepAlive" box in the HTTP Request Sampler (or even better  HTTP
Request Defaults
<https://www.blazemeter.com/blog/why-its-so-important-use-jmeters-http-request-defaults/>  
so the changes would be propagated to all HTTP Request samplers)

If you're talking about  Java Request
<https://jmeter.apache.org/usermanual/component_reference.html#Java_Request>  
sampler - unfortunately no one will be able to help unless you share your
code, I can only recommend using a profiler tool like  YourKit
<https://www.yourkit.com/java/profiler/>  , it should be able to detect
obvious memory leaks like not closed connection.



--
Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]