selenium: selenuim server node 3.14.0 failed to start new session for Edge

selenium server node failed to start new session for edge

OS: Windows 10

Selenium Version: 3.14.0

Browser: Edge

Browser Version:
44.17763.1.0 WebDriver version: 10.0.17763

Expected Behavior -

New session starts for edge browser.

Actual Behavior -

Node fails to create new session with error in log:

[04:37:59.452] - Listening on http://127.0.0.1:33791/ 
[04:37:59.452] - Listening on http://[::1]:33791/ 
[04:37:59.936] - Invalid capabilities 
The following JSON wire protocol command endpoint is not allowed when server is running in W3C mode.
GET /shutdown

Steps to reproduce -

  1. Run selenium-standalone-server.jar on VM1 java -jar selenium-server-standalone-3.14.0.jar -debug -role hub
  2. Run selenium-standalone-server.jar on VM2 as Edge node java “-Dwebdriver.edge.driver=C://Windows/System32/MicrosoftWebDriver.exe” “-Dwebdriver.edge.driver=C://selenium/driverlog” -jar selenium-server-standalone-3.14.0.jar -debuf -role node -nodeConfig edge_node_config.json edge_node_config.json contents:
{
  "browserTimeout": 0,
  "capabilities": [
    {
      "browserName": "MicrosoftEdge",
      "browserVersion": "44.17743.1.0",
      "maxInstances": 1,
      "plaftormName": "win10",
      "platform": "WIN10",
      "platformName": "WIN10",
      "seleniumProtocol": "WebDriver"
    }
  ],
  "custom": {
  },
  "debug": true,
  "downPollingLimit": 2,
  "enablePlatformVerification": false,
  "host": "192.168.1.36",
  "hubHost": "192.168.1.42",
  "hubPort": 4444,
  "id": "http://192.168.1.36:7890",
  "maxSession": 5,
  "nodePolling": 5000,
  "nodeStatusCheckTimeout": 5000,
  "port": 7890,
  "proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
  "register": true,
  "registerCycle": 5000,
  "remoteHost": "http://192.168.1.36:7890",
  "role": "node",
  "servlets": [
  ],
  "timeout": 1800,
  "unregisterIfStillDownAfter": 60000,
  "withoutServlets": [
  ]
}

So this probably related to one of last changes which supported --jwp & --w3c args for MicrosoftWebDriver, but if I manually add --jwp flag to executable path it will fail create instance of EdgeDriverService. Is there any way to strictly define which arguments should be passed to executable of EdgeDriver?

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 7
  • Comments: 30 (8 by maintainers)

Most upvoted comments

@thejohnjansen Thanks for help. I found out how to set everything up