Contributions
Re: [Possible Bug] SoapUI 5 is setting default proxyselector to null
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.3.7KViews0likes1CommentRe: [Possible Bug] SoapUI 5 is setting default proxyselector to null
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.3.7KViews1like1Comment