I ran across a similar problem a bit over a year ago.  The solution was to 
configure the DNS server for correct reverse-DNS queries.  NETBIOS is used only 
when Windows can't get information from the DNS server.

-----Original Message-----
From: 张为东(为东) [mailto:[email protected]] 
Sent: Wednesday, August 27, 2014 9:24 PM
To: 'JMeter Users List'; [email protected]
Subject: 答复: JMeter sends https request delayed due to netbios lookup

Hi Philippe,

 

C:\Users\weidong.zwd>java -version

java version "1.7.0_25"

Java(TM) SE Runtime Environment (build 1.7.0_25-b17)

Java HotSpot(TM) Client VM (build 23.25-b01, mixed mode, sharing)

 

Platform:

Win7 professional SP1 64bit

 

For http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6450279 you mentioned 
in bug#54449, seems it’s resolved in 2006……

 

Thanks,

--Weidong

-----邮件原件-----
发件人: Philippe Mouawad [mailto:[email protected]]
发送时间: 2014年8月28日 5:31
收件人: JMeter Users List
主题: Re: JMeter sends https request delayed due to netbios lookup

 

Hello,

You maybe facing this issue:

 

-  <https://issues.apache.org/bugzilla/show_bug.cgi?id=54449>
https://issues.apache.org/bugzilla/show_bug.cgi?id=54449

 

There is currently a discussion on dev list related to how httpclient 4.2.3 
uses INetaddress.getHostByName (which makes reverse lookup that could explain 
this issue) and could use a new method from jdk7.

 

Can you attach all details you jave on this issue if you are in the same 
conditions.

 

Regards

Philippe M.

@philmdot

On Wednesday, August 27, 2014, Shmuel Krakower < <mailto:[email protected]> 
[email protected]> wrote:

 

> I didn't notice I sent email directly to you.

> Better continue communication at the users list.

> 

> Not sure why HC4 behaves like that.

> Maybe someone else can explain.

> 

>  <http://www.beatsoo.org> www.beatsoo.org - free application 
> performance
monitoring from world 

> wide locations.

> On Aug 27, 2014 5:39 AM, "张为东(为东)" <[email protected]

> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:

> 

>> Shmuel,

>> 

>> 

>> 

>> Is it the same with different Implementations of the HTTP Sampler

>> (JAVA/HC3.1/HC4)?

>> 

>> [Weidong]Based on your advice below, I changed implementation of the

>> HTTP Sampler, found that there is no netbios lookup when I use

>> JAVA/HC3.1(I used

>> HC4 in the below case).

>> 

>> So what’s the difference among JAVA/HC3.1/HC4/blank value? Seems

>> HC3.1 is obsoleted than HC4.

>> 

>>    - HTTPClient3.1 - uses Apache Commons HttpClient 3.1. This is no

>>    longer being developed, and support for this may be dropped in a
future

>>    JMeter release.

>>    - HTTPClient4 - uses Apache HttpComponents HttpClient 4.x

>> 

>> 

>> 

>> Does it work differently if you put IP/DNS as the host in the HTTP

>> sampler instead of hostname?

>> 

>> [Weidong]I had already put IP address instead of hostname in the http

>> sampler.

>> 

>> 

>> 

>> 

>> 

>> *发件人:* Shmuel Krakower [mailto:[email protected]

>> <javascript:_e(%7B%7D,'cvml','[email protected]');>]

>> *发送时间:* 2014年8月26日 22:08

>> *收件人:* 张为东(为东)

>> *主题:* Re: 答复: JMeter sends https request delayed due to netbios

>> lookup

>> 

>> 

>> 

>> Is it the same with different Implementations of the HTTP Sampler

>> (JAVA/HC3.1/HC4)?

>> 

>> Does it work differently if you put IP/DNS as the host in the HTTP

>> sampler instead of hostname?

>> 

>> 

>> Shmuel Krakower.

>> 

>>  <http://www.Beatsoo.org> www.Beatsoo.org - re-use your jmeter 
>> scripts
for application 

>> performance monitoring from worldwide locations for free.

>> 

>> 

>> 

>> On Tue, Aug 26, 2014 at 4:28 PM, 张为东(为东)
<[email protected] 

>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:

>> 

>> Shmuel, I’d like to figure out the reason why JMeter sends netbios

>> lookup

>> 3 times in this case.

>> 

>> 

>> 

>> On the other hand, I think it’s not related to the connection

>> timeout, the server side works well, the client side cost more

>> seconds to send next packet.

>> 

>> 

>> 

>> *发件人:* Shmuel Krakower [mailto:[email protected]

>> <javascript:_e(%7B%7D,'cvml','[email protected]');>]

>> *发送时间:* 2014年8月26日 21:09

>> *收件人:* JMeter Users List; 张为东(为东)

>> *主题:* Re: JMeter sends https request delayed due to netbios lookup

>> 

>> 

>> 

>> As you can see - it failed to connect the destination host.

>> 

>> You should be able to control the connect part to timeout if it

>> doesn't get a valid connection in a shorter time via the Connect Timeout:

>> 

>>  
>> <http://jmeter.apache.org/usermanual/component_reference.html#HTTP_Re
>> q>
http://jmeter.apache.org/usermanual/component_reference.html#HTTP_Req

>> uest

>> 

>> 

>> Shmuel Krakower.

>> 

>>  <http://www.Beatsoo.org> www.Beatsoo.org - re-use your jmeter 
>> scripts
for application 

>> performance monitoring from worldwide locations for free.

>> 

>> 

>> 

>> On Tue, Aug 26, 2014 at 3:17 PM, 张为东(为东)
<[email protected] 

>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:

>> 

>> Hi Experts,

>> 

>> 

>> 

>> I encountered one issue that when JMeter sends a https request to

>> server, it cost mostly 4 seconds during the session, it’s too long……. 

>> I had captured the packet data by wireshark, you can have a look

>> below or attachment.

>> 

>> 

>> 

>> Source IP(https client-JMeter):10.68.33.195

>> 

>> Destination IP(https server):10.125.199.69

>> 

>> 

>> 

>> For packet #1037, #1252 and #1404, JMeter tried 3 times to do netbios

>> lookup, it cost 3 seconds, it’s unexpected for me;

>> 

>> But the server side handle the https request quickly, it cost around

>> 0.1s, it’s expected for me.

>> 

>> 

>> 

>> Thanks,

>> 

>> Weidong

>> 

>> 

>> 

>> ---------------------------------------------------------------------

>> To unsubscribe, e-mail:  <mailto:[email protected]>
[email protected]

>> <javascript:_e(%7B%7D,'cvml','[email protected]');>

>> For additional commands, e-mail:  
>> <mailto:[email protected]>
[email protected] 

>> <javascript:_e(%7B%7D,'cvml','[email protected]');>

>> 

>> 

>> 

>> 

>> 

> 

 

--

Cordialement.

Philippe Mouawad.

Reply via email to