When running selenium remotedriver, there is a problem with nativeconstructoraccessorimpl Newinstance0 bad sessionnotcreatedexception error

Reprinted address ：http://www.voidcn.com/article/p-ccdzafzn-bto.html

Error message ：

Exception in thread "main" org.openqa.selenium.SessionNotCreatedException: Unable to create new service: ChromeDriverService
Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T19:05:32.194Z'
System info: host: 'RAJESHW10', ip: '169.254.3.253', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_91'
Driver info: driver.version: unknown
Command duration or timeout: 316 milliseconds
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

explain ：

This error does give us a hint about the error , As shown below ：

> Threads “main” The abnormal org.openqa.selenium.SessionNotCreatedException： Unable to create new service ：ChromeDriverService： Unable to create new service ：ChromeDriverService Indicates that a new session has not been started .
> Driver information ：driver.version：unknown：driver.version：unknown Indicates that there is no call chromedriver Binary .
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)：sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method), It comes from any of the following ：

• java.lang.RuntimeException： Exception in constructor ： The occurrence of this exception is unique to reflection . Usually , It is impossible to write code that ignores checked exceptions , Because it doesn't compile at all .
• java.lang.reflect.InvocationTargetException： If you throw InvocationTargetException, It means that the method is called . This exception does not indicate a problem with the reflection package or its usage .
• java.lang.IllegalArgumentException： If the constructor passes a parameter of the wrong type , Throw out IllegalArgumentException.

Conclusion ：

From the above ponints Obviously ,Selenium-Java client ,JDK,ChromeDriver Binaries and Chrome The version of is not compatible .

The solution is as follows ：

Update with the latest version JDK(JDK 8u152)> Update with the latest version Selenium-Java client (Selenium-Java v3.8.1)> Update with the latest version ChromeDriver Binary (ChromeDriver v2.34)> Update with the latest version ChromeDriver Binary (Chrome v63.0)