Web Service Execution Step (XML) Error

[Anon Anon]

I am trying to invoke a web service through Web Service Execution Step (XML)

 

WSDL - http://wsf.cdyne.com/WeatherWS/Weather.asmx?WSDL

 

When i try to load WSDL i am getting below mentioned error :

java.net.UnknownHostException: wsf.cdyne.com

  at java.net.InetAddress.getAllByName0(Unknown Source)

  at java.net.InetAddress.getAllByName(Unknown Source)

  at java.net.InetAddress.getAllByName(Unknown Source)

  at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45)

  at org.apache.http.impl.conn.DefaultClientConnectionOperator.resolveHostname(DefaultClientConnectionOperator.java:278)

  at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:162)

 

But it is working fine on SOAP UI on the same system.I am able to invoke the service and perform all the operations.

 

Please advice.

[Anon Anon]

Moreover, I am getting the same error in every step of Web/Web Services Category.

 

And i can open the link in web browser plus it is working fine on SOAP UI.

[Prem Bairoliya]

Try setting the following in your Workstation.vmoptions file, restarting the Workstation & trying again

-Djava.net.preferIPv4Stack=true

[Anon Anon]

Tried..Didn't work.

[Prem Bairoliya]

Does your environment use Proxy server to connect to Weather Web Service

If so, use the information available at the following location to configure a web proxy companion

 

https://docops.ca.com/devtest-solutions/9-1/en/reference/companion-descriptions/configure-devtest-to-use-a-web-proxy-companion/

[Anon Anon]

Now I am confused, how come i am able to connect to the web service with SOAPUI using the same settings.

Let me check for such settings anyways.

[Prem Bairoliya]

SOAPUI maybe able to connect as it has a default option of Automatically determining proxy setting

Proxy setting

How the proxy is determined. Automatic tries to automatically determine proxy by looking at Java settings, environment variables, browser settings and operating system settings. None turns off the proxy. Manual uses the host, port and excludes entered below.

[Anon Anon]

Thanks! It worked

[Legacy User]

Not sure why your host is not resolving.  Can you try a test using a REST step only for the case where you are retrieving the WSDL? 

 

I get a slightly different response when using DevTest v9.1.  The endpoint resolves itself.  If I send the request as a Web Service Execution XML (HTTP Version 1.1 or 1.0 and Soap Version 1.1), I receive an HTTP 500 fault indicating the server did not recognize the HTTP SOAPAction header -- which makes sense since this is really a REST call to the IIS server with no SOAP body.  If I swap to Soap Version 1.2, I receive an HTTP 500 fault indicating the server was unable to process the request due to a missing root element.

If I send the request from a REST step, I get the WSDL.

[Anon Anon]

Still getting the same error

[Legacy User]

It is unclear to me why you are seeing the error.  As you can see from the screenshots, I was able to access the endpoint. The endpoint was unhappy with the format of the HTTP request when using a WS Execution step, but both steps show the endpoint responding.