Forum Discussion

smurf667's avatar
Occasional Visitor
8 years ago

SoapUI Maven plugin 5.2.1 bug report

We've found that after the SoapUI Maven plugin has run the default ProxySelector in the Java network stack is messed up. Looking at the code it appears that the plugin sets the proxy selector to null (line 186, see e.g.


While not explicitly stated in the JavaDoc, I think it should not be set to null. If SoapUI needs a null value here, it should restore the original proxy selector that was nulled once the plugin finished. With the proxy selector being null, other code running after the plugin fails, e.g. Apache HttpClient 4.5.2 cannot work any more and produces a NullPointerException.

1 Reply

  • ascheman's avatar
    Occasional Visitor

    Is there anything new to this problem?


    I am using soapui-maven-plugin 5.3.0 and I was fighting more than half a day with SonarQube problems. SonarQube Plugin starts after SoapUi and failed to connect the server:


    Caused by: java.lang.IllegalStateException: Fail to download libraries from server
    at org.sonarsource.scanner.api.internal.Jars.downloadFiles(
    at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory$
    ... 30 more
    Caused by: java.lang.NullPointerException: proxySelector == null
    at org.sonarsource.scanner.api.internal.shaded.okhttp.Address.<init>(
    at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.HttpEngine.createAddress(
    at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.HttpEngine.<init>(
    at org.sonarsource.scanner.api.internal.shaded.okhttp.RealCall.getResponse(
    at org.sonarsource.scanner.api.internal.shaded.okhttp.RealCall$ApplicationInterceptorChain.proceed(
    at org.sonarsource.scanner.api.internal.shaded.okhttp.RealCall.getResponseWithInterceptorChain(
    at org.sonarsource.scanner.api.internal.shaded.okhttp.RealCall.execute(
    at org.sonarsource.scanner.api.internal.ServerConnection.callUrl(
    at org.sonarsource.scanner.api.internal.ServerConnection.downloadString(
    at org.sonarsource.scanner.api.internal.Jars.downloadFiles(



    It turned out that the error only occurs when I have a soapui-settings.xml (without any proxy settings). I could not even override the proxy params with explicit <soapuiProperties> in the Maven plugin configuration.


    I would expect the following:

    - Explicit settings in the Maven plugin configuration should override settings from a settings file!

    - If neither explicit settings or a settings file is provided, system settings should be used (at least for Proxies)

    - Switching on debug output should report used settings!

    - If the SOAP UI plugin (or SOAP UI itself) is changing any default (proxy settings) it should report this as a log entry (at least when run with debug output/Maven -X flag)

    - The SOAP UI should reset to the former state when finishing