Bug 63858 - DNS Cache Manager - Static Host Table in distributed mode
Summary: DNS Cache Manager - Static Host Table in distributed mode
Status: NEEDINFO
Alias: None
Product: JMeter
Classification: Unclassified
Component: HTTP (show other bugs)
Version: 5.1.1
Hardware: Macintosh Mac OS X 10.1
: P2 major (vote)
Target Milestone: JMETER_5.2
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-17 10:37 UTC by Auro
Modified: 2019-11-12 16:44 UTC (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Auro 2019-10-17 10:37:30 UTC 
We are using jmeter in distributed mode. 
We put on the script a DNS Cache Manager on the test plan root, configured with "Clear cache each iteration" flagged, "Use custom DNS resolver" ON, Static host table with one entry like hostname - ip address. All the HTTP sampler use HTTPClient4 implementation and https as protocol.

On the first run all seems working well, but is we canche the hostname on the Static host table, save the script and do a second run, we have the following error on the http sampler view result tree:

java.lang.NullPointerException
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:115)
	at org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl$JMeterDefaultHttpClientConnectionOperator.connect(HTTPHC4Impl.java:336)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:374)
	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
	at org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.executeRequest(HTTPHC4Impl.java:843)
	at org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.sample(HTTPHC4Impl.java:574)
	at org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:67)
	at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1231)
	at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1220)
	at org.apache.jmeter.threads.JMeterThread.doSampling(JMeterThread.java:622)
	at org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:546)
	at org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:486)
	at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:253)
	at java.lang.Thread.run(Thread.java:748) 

It seems like the new hostname is not correctly set on the jmeter slave.
Comment 1 Auro 2019-10-17 10:41:48 UTC 
Sorry, I mean

"On the first run all seems working well, but if we change the hostname"
Comment 2 Philippe Mouawad 2019-11-11 18:23:31 UTC 
(In reply to Auro from comment #1)
> Sorry, I mean
> 
> "On the first run all seems working well, but if we change the hostname"

Hello,
1/ Can you check if issue is fixed with JMeter 5.2 ? 
2/ Can you clarify the steps ?
Do you have this issue in GUI or Non GUI mode ? Does it happens when in GUI mode you change hostname and run again without quitting JMeter ?

Thank you
Comment 3 Auro 2019-11-12 16:44:50 UTC 
Hi,

1/ Can you check if issue is fixed with JMeter 5.2 ? Unfortunately no, the slaves are on a server room behind a firewall and I can't change them.

2/ Can you clarify the steps ? Sure

Do you have this issue in GUI or Non GUI mode ? In GUI Mode

Does it happens when in GUI mode you change hostname and run again without quitting JMeter ? Exactly!, but the slavers are always running waiting for new master connections so they don't restart between tests.