Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

10.2.4 throws error when using --seleniumPort #106

Closed
drphrozen opened this issue Oct 17, 2016 · 4 comments · Fixed by #108
Closed

10.2.4 throws error when using --seleniumPort #106

drphrozen opened this issue Oct 17, 2016 · 4 comments · Fixed by #108

Comments

@drphrozen
Copy link

We get an Unrecognized option: -port when using --seleniumPort.

c:\Jenkins\jobs\Website E2E\workspace>node_modules\.bin\webdriver-manager start --seleniumPort 14444 --ignore_ssl
[08:39:24] I/start - java -port 14444 -Dwebdriver.chrome.driver=c:\Jenkins\jobs\Website E2E\workspace\node_modules\protractor\node_modules\webdriver-manager\selenium\chromedriver_2.24.exe -Dwebdriver.gecko.driver=c:\Jenkins\jobs\Website E2E\workspace\node_modules\protractor\node_modules\webdriver-manager\selenium\geckodriver-v0.9.0.exe -jar c:\Jenkins\jobs\Website E2E\workspace\node_modules\protractor\node_modules\webdriver-manager\selenium\selenium-server-standalone-2.53.1.jar
[08:39:24] I/start - seleniumProcess.pid: 4444
Unrecognized option: -port
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
[08:39:24] I/start - Selenium Standalone has exited with code 1

I tried reverting to 10.2.3 using shrinkwrap, which solved the issue.

OS: Windows 10
Java: 1.8.0_65

@attila123
Copy link

I can confirm it is broken. I tried it on Linux. Got the same error message. Was just about to report it.

@kevin-smets
Copy link
Contributor

kevin-smets commented Oct 17, 2016

Same issue on OS X (obviously), but well, added now :).

kevin-smets added a commit to kevin-smets/webdriver-manager that referenced this issue Oct 17, 2016
@axelssonHakan
Copy link

Have something similar with options for update.
The option --standalone false doesn't seem to work. It's uses the default value true instead.

Is this issue the same or should I file a new?

@kevin-smets
Copy link
Contributor

@cnishina awesome, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants