Forum Discussion
- jimsefton9 years agoOccasional Visitor
Hi,
Any update on this. I am getting the same error... tried using the following workaround but it's not working:
import org.openqa.selenium.WebDriver import org.openqa.selenium.firefox.FirefoxDriver ProxySelector proxy = ProxySelector.getDefault(); ProxySelector.setDefault(proxy); WebDriver driver = new FirefoxDriver(); driver.get("http://localhost ") log.info("Pagee is: " + driver.getTitle()) driver.quit()
Any suggestions of a fix or workaround would be appreciated. Thanks
- wind198620069 years agoNew Contributor
ProxySelector proxy = ProxySelector.getDefault(); ProxySelector.setDefault(proxy);
This will do nothing. You need to get
ProxySelector proxy = ProxySelector.getDefault();
before you run SOAPUI to save proxy and then
ProxySelector.setDefault(proxy);
to reset it and make sure proxy won't be null when you initiate selenium webdriver.
- annamalairobins6 years agoNew Member
This workaround helped me resolve the issue, I have been wondering what could be the issue for last 1.5 years.
Thank you!
- wind198620069 years agoNew Contributor
Is there any plan from SoapUI Open Source team to fix this?
I have been using the work around solution for 2 years but recently we decide to enable paralell execution for our test to improve performance.
That means if we have no real fix for this issue, then it might still interupt webdriver instance like race codition.
This is actually blocking SOAPUI to be considered as API testing solution for many projects where selenium is also selected.
Please consider to provide a fix on it. It will be such a easy fix.
Or at least tell me, in which class SOAPUI api actually set the proxy to null so I can overwite it in my project.
I appreciate any update you can provide.
- class1018 years agoFrequent Visitor
Hello I just registered in here to share on this issue that I consider blocking and I believe the Smartbear developers completely under estimate the severity of it, so at least the error log of our Jenkins integration build will be search friendly and people having the same issue will voice up until they finally decide to fix.
Small introduction about myself, I'm responsible on DevOps operations in a development team at Accenture and the principal tools I'm operating with are;
Maven 3.3.9 Jenkins 2.x and soapui-maven-plugin 5.2.1 => PROXY BUG IN JENKINS => proxySelector == null
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.0.1:sonar (default-cli) on project parent: Fail to download libraries from server: proxySelector == null -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
This has been hard for me to track the real cause of this issue and this thread entirely reveal the truth, I was smelling an issue around this plugin but not Sonar, and this is quite frustrating to see it has been known since more than a year ago !@# (my feeling)
I'm sorry but in our Maven setup, we require a proxy to be set, but if you change it to null without our consent, 1) it's wrong 2) you are causing side issues in Jenkins/Maven integration builds for us, and Selenium for the people above me in this post, and probably lots of issues.
Related Content
- 21 days agoStoplight
Recent Discussions
- 6 hours agocodehausss