使用docker-compose在网格上动态执行我的套件时,出现以下异常stacktrace:
org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
03:52:47 Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
03:52:47 System info: host: 'ip-10-33-0-63', ip: '10.33.0.63', os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-1069-aws', java.version: '1.8.0_151'
03:52:47 Driver info: driver.version: RemoteWebDriver
03:52:47 at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:573)
03:52:47 at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:213)
03:52:47 at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:131)
03:52:47 at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:144)
03:52:47 at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
03:52:47 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
03:52:47 at java.lang.reflect.Method.invoke(Method.java:498)
03:52:47 at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:131)
03:52:47 at org.testng.internal.MethodInvocationHelper.invokeMethodConsideringTimeout(MethodInvocationHelper.java:61)
03:52:47 at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:511)
03:52:47 at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:241)
03:52:47 at org.testng.internal.Invoker.invokeMethod(Invoker.java:581)
03:52:47 at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:792)
03:52:47 at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1103)
03:52:47 at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:140)
03:52:47 at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:122)
03:52:47 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
03:52:47 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
03:52:47 at java.lang.Thread.run(Thread.java:748)
03:52:47 Caused by: java.net.ConnectException: Failed to connect to /10.33.0.220:4444
03:52:47 at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:247)
03:52:47 at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:165)
03:52:47 at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:257)
03:52:47 at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:135)
03:52:47 at okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:114)
03:52:47 at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
03:52:47 at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
03:52:47 at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
03:52:47 at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
03:52:47 at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
03:52:47 at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
03:52:47 at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
03:52:47 at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
03:52:47 at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:126)
03:52:47 at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
03:52:47 at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
03:52:47 at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200)
03:52:47 at okhttp3.RealCall.execute(RealCall.java:77)
03:52:47 at org.openqa.selenium.remote.internal.OkHttpClient.execute(OkHttpClient.java:103)
03:52:47 at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:105)
03:52:47 at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:74)
03:52:47 at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:136)
03:52:47 at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552)
03:52:47 Caused by: java.net.ConnectException: Connection refused (Connection refused)
03:52:47 at java.net.PlainSocketImpl.socketConnect(Native Method)
03:52:47 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
03:52:47 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
03:52:47 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
03:52:47 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
03:52:47 at java.net.Socket.connect(Socket.java:589)
03:52:47 at okhttp3.internal.platform.Platform.connectSocket(Platform.java:129)
03:52:47 at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:245)
这是在执行时发生的:
return (new RemoteWebDriver(new URL(url), new FirefoxOptions()));
镀铬也会发生这种情况。我最近将硒升级到了最新版本,即3.141.59。
docker-compose.yml
是:
version: "3"
services:
selenium-hub:
image: selenium/hub:3.141.59-bismuth
container_name: selenium-hub
ports:
- "4444:4444"
environment:
- GRID_BROWSER_TIMEOUT=30
chrome:
image: selenium/node-chrome:3.141.59-bismuth
depends_on:
- selenium-hub
environment:
- HUB_HOST=selenium-hub
- HUB_PORT=4444
firefox:
image: selenium/node-firefox:3.141.59-bismuth
depends_on:
- selenium-hub
environment:
- HUB_HOST=selenium-hub
- HUB_PORT=4444
volumes:
- "/dev/shm:/dev/shm"
这既发生在Jenkins中,也发生在我从cmd在系统中执行它时。我不确定该问题是否与硒或网络有关。如果还有解决方案的其他链接,请在此处共享。感谢您的任何帮助。
更新编辑:
启动:
1)通过 mvn clean install -DskipTests = true
构建项目(使用maven-assembly-plugin)。2)启动网格:sudo docker-compose up -d --scale chrome = 5 --scale firefox = 3
3)运行可执行jar。
4)删除网格:sudo docker-compose down
更新:
添加中心配置:
Config for the hub :
browserTimeout : 30
debug : false
jettyMaxThreads : -1
host : 192.168.80.2
port : 4444
role : hub
timeout : 1800
cleanUpCycle : 5000
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
newSessionWaitTimeout : -1
throwOnCapabilityNotPresent : true
registry : org.openqa.grid.internal.DefaultGridRegistry
The final configuration comes from:
the default :
browserTimeout : 0
debug : false
host : 0.0.0.0
port : 4444
role : hub
timeout : 1800
cleanUpCycle : 5000
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
newSessionWaitTimeout : -1
throwOnCapabilityNotPresent : true
registry : org.openqa.grid.internal.DefaultGridRegistry
updated with command line options:
-role hub -hubConfig /opt/selenium/config.json
and configuration loaded from /opt/selenium/config.json:
{
"host": "0.0.0.0",
"port": 4444,
"role": "hub",
"maxSession": 5,
"newSessionWaitTimeout": -1,
"capabilityMatcher": "org.openqa.grid.internal.utils.DefaultCapabilityMatcher",
"throwOnCapabilityNotPresent": true,
"jettyMaxThreads": -1,
"cleanUpCycle": 5000,
"browserTimeout": 30,
"timeout": 1800,
"debug": false
}
添加节点配置:
browserTimeout: 30
debug: false
jettyMaxThreads: -1
host: 192.168.80.6
port: 5555
role: node
timeout: 1800
cleanUpCycle: 5000
maxSession: 1
capabilities: Capabilities {applicationName: , browserName: chrome, maxInstances: 1, platform: LINUX, platformName: LINUX, seleniumProtocol: WebDriver, server:CONFIG_UUID: d949d886-61f4-4a3a-93f9-c2a..., version: 70.0.3538.110}
downPollingLimit: 2
hub: http://selenium-hub:4444/grid/register
id: http://192.168.80.6:5555
nodePolling: 5000
nodeStatusCheckTimeout: 5000
proxy: org.openqa.grid.selenium.proxy.DefaultRemoteProxy
register: true
registerCycle: 5000
remoteHost: http://192.168.80.6:5555
unregisterIfStillDownAfter: 60000
答案 0 :(得分:0)
此错误消息...
org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
03:52:47 Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
03:52:47 System info: host: 'ip-10-33-0-63', ip: '10.33.0.63', os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-1069-aws', java.version: '1.8.0_151'
03:52:47 Driver info: driver.version: RemoteWebDriver
...表示 WebDriver 无法启动/产生新的 RemoteWebDriver 会话。
我在您的配置或代码行中没有看到任何重大问题。但是,您的主要问题似乎是所使用的二进制版本之间的不兼容性:
Test
。答案 1 :(得分:0)
我通过遵循本文的最后评论解决了相同的问题。 Docker Container cannot reach localhost port 4444. Why though?
在服务所在的docker-compose.yaml文件中,集线器就是所谓的集线器。使用该名称来指定remotewebdriver的网址。
只需将'localhost:4444 / wd / hub'更改为'seleniumhub:4444 / wd / hub'