No i was not using IP's. I was trying to connect to a site which was
non-existent. I will also try with IP's and see how it behaves. So i
guess the connect timeout value depends on other factors such DNS
resolution as well. I guess thats why it does not have any default value
? Anyone disagrees with it ? Please correct me if i am wrong.
Thanks
Jatin
Trenton Lipscomb wrote:
Are you using IPs? If not, perhaps in case 1 you're hitting the connect
timeout and in case #2 you're running into a DNS timeout of 20 seconds which
then fails the whole thing.
*trenton
Sent from Itasca, Illinois, United States
On Thu, Dec 24, 2009 at 11:28 PM, Jatin Davey <[email protected]> wrote:
Ok , I found out testing a non-existent site. The default value is around
20 - 21 secs.
One more thing that i am seeing is the following :
1. If i set the default connect timeout value to say , 5000 millisecs (In
the HTTP request sampler) , the requests to the same non-existent site is
getting timed out in 5 secs which is correct.
2. If i set the default connect timeout value to say , 30000 millisecs (In
the HTTP request sampler) , the requests to the same non-existent site is
getting timed out in 20 secs and not in 30 secs.
Is the value mentioned in the HTTP request sampler not supposed to override
the default values. Please let me know.
Thanks
Jatin
Jatin Davey wrote:
Hi
If i dont mention the default timeout values in the connect and response
fields in a HTTP request samplers then what values are taken as default.
Thanks
Jatin
---------------------------------------------------------------------
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]
