Scala gatlinglocaladdresses导致超时
我们希望能够在为运行性能测试而设置的Azure虚拟机上循环使用可用的IP地址 我们只使用主本地主机地址的协议代码工作正常:Scala gatlinglocaladdresses导致超时,scala,azure,networking,gatling,Scala,Azure,Networking,Gatling,我们希望能够在为运行性能测试而设置的Azure虚拟机上循环使用可用的IP地址 我们只使用主本地主机地址的协议代码工作正常: var httpProtocol = io.gatling.http.Predef.http .baseUrl(baseUrl) .inferHtmlResources() .acceptHeader("*/*") .userAgentHeader("Mozilla/5.0 (Windows NT 10.0; Win64; x64)
var httpProtocol = io.gatling.http.Predef.http
.baseUrl(baseUrl)
.inferHtmlResources()
.acceptHeader("*/*")
.userAgentHeader("Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36")
.maxConnectionsPerHostLikeChrome
但是,当我们将此更改为尝试在可用IP(在NIC和pingable上配置)之间循环时,我们会收到大量错误“i.n.c.ConnectTimeoutException:connection Timeout:blah.mydomain.co.uk/11.22.33.44:443”(尽管前一两个用户似乎还可以):
两者都继续使用此代码:
setUp(usertype1.inject(
rampConcurrentUsers(0) to (maxConcurrentUsers) during (rampUpDownTime),
constantConcurrentUsers(maxConcurrentUsers) during (mainTestTime),
rampConcurrentUsers(maxConcurrentUsers) to (0) during (rampUpDownTime)
)
).protocols(httpProtocol);
当我们在同一台机器上使用不同的IP时,是什么导致这些超时?只能是网络问题(路由、防火墙等),而不是Gatling问题
setUp(usertype1.inject(
rampConcurrentUsers(0) to (maxConcurrentUsers) during (rampUpDownTime),
constantConcurrentUsers(maxConcurrentUsers) during (mainTestTime),
rampConcurrentUsers(maxConcurrentUsers) to (0) during (rampUpDownTime)
)
).protocols(httpProtocol);