Highlighted
Absent Member.
Absent Member.
2446 views

LoadRunner 9.5 Web Services Testing

I am attempting to run a test on one web service and I am getting an error that I cannot seem to correct. 

 

This is what I get at the end of the run (which is only one user and iteration).

 

Action.c(23): Notify: Saving Parameter "response = <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Header/><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server.generalException</faultcode><faultstring>org.xml.sax.SAXException: WSWS3066E: Error: Expected &apos;envelope&apos; but found  definitions Message being parsed: dl:operation name=&quot;newOperation1&quot;&gt;&lt;wsdl:input message=&quot;impl:newOperation1Request&quot; name=&quot;newOperation1Request&quot;&gt;&lt;/wsdl:input&gt;&lt;wsdl:output message=&quot;impl:newOperation1Response&quot; name=&quot;newOperation1Response&quot;&gt;&lt;/wsdl:output&gt;&lt;/wsdl:operation&gt;&lt;/wsdl:portType&gt;&lt;wsdl:binding name=&quot;CHFS_Test1SOAPSoapBinding&quot; type=&quot;impl:CHFS_Test1&quot;&gt;&lt;wsaw:UsingAddressing wsdl:required=&quot;false&quot;&gt;&lt;/wsaw:UsingAddressing&gt;&lt;wsdlsoap:binding style=&quot;document&quot; transport=&quot;http://schemas.xmlsoap.org/soap/http&quot;&gt;&lt;/wsdlsoap:binding&gt;&lt;wsdl:operation name=&quot;newOperation1&quot;&gt;&lt;wsdlsoap:operation soapAction=&quot;&quot;&gt;&lt;/wsdlsoap:operation&gt;&lt;wsdl:input name=&quot;newOperation1Request&quot;&gt;&lt;wsdlsoap:body use=&quot;literal&quot;&gt;&lt;/wsdlsoap:body&gt;&lt;/wsdl:input&gt;&lt;wsdl:output name=&quot;newOperation1Response&quot;&gt;&lt;wsdlsoap:body use=&quot;literal&quot;&gt;&lt;/wsdlsoap:body&gt;&lt;/wsdl:output&gt;&lt;/wsdl:operation&gt;&lt;/wsdl:binding&gt;&lt;wsdl:service name=&quot;CHFS_Test1&quot;&gt;&#xd;- &lt;wsdl:port binding=&quot;impl:CHFS_Test1SOAPSoapBinding&quot; name=&quot;CHFS_Test1SOAP&quot;&gt;&lt;wsdlsoap:address location=&quot;http://infosvrnprod.state.ky.us:9080/wisd/CHFS_Test1/CHFS_Test1&quot;&gt;&lt;/wsdlsoap:address&gt;&lt;/wsdl:port&gt;&lt;/wsdl:service&gt;&lt;/wsdl:definitions&gt;</faultstring></soapenv:Fault></soapenv:Body></soapenv:Envelope>"

Action.c(23): Error: The reason for the SOAP fault is: "org.xml.sax.SAXException: WSWS3066E: Error: Expected 'envelope' but found  definitions Message being parsed: dl:operation name="newOperation1"&gt;&lt;wsdl:input message="impl:newOperation1Request" name="newOperation1Request"&gt;&lt;/wsdl:input&gt;&lt;wsdl:output message="impl:newOperation1Response" name="newOperation1Response"&gt;&lt;/wsdl:output&gt;&lt;/wsdl:operation&gt;&lt;/wsdl:portType&gt;&lt;wsdl:binding name="CHFS_Test1SOAPSoapBinding" type="impl:CHFS_Test1"&gt;&lt;wsaw:UsingAddressing wsdl:required="false"&gt;&lt;/wsaw:UsingAddressing&gt;&lt;wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"&gt;&lt;/wsdlsoap:binding&gt;&lt;wsdl:operation name="newOperation1"&gt;&lt;wsdlsoap:operation soapAction=""&gt;&lt;/wsdlsoap:operation&gt;&lt;wsdl:input name="newOperation1Request"&gt;&lt;wsdlsoap:body use="literal"&gt;&lt;/wsdlsoap:body&gt;&lt;/wsdl:input&gt;&lt;wsdl:output name="newOperation1Response"&gt;&lt;wsdlsoap:body use="literal"&gt;&lt;/wsdlsoap:body&gt;&lt;/wsdl:output&gt;&lt;/wsdl:operation&gt;&lt;/wsdl:binding&gt;&lt;wsdl:service name="CHFS_Test1"&gt;
- &lt;wsdl:port binding="impl:CHFS_Test1SOAPSoapBinding" name="CHFS_Test1SOAP"&gt;&lt;wsdlsoap:address location="http://infosvrnprod.state.ky.us:9080/wisd/CHFS_Test1/CHFS_Test1"&gt;&lt;/wsdlsoap:address&gt;&lt;/wsdl:port&gt;&lt;/wsdl:service&gt;&lt;/wsdl:definitions&gt;"

Action.c(23): Error: SOAP request "SOAP Request" execution failed

 

Prior to the 3 messages above I first get

 

Action.c(23):     HTTP/1.1 500 Internal Server Error\r\n

 

and

 

Action.c(23):     XException: WSWS3066E: Error: Expected &apos;envelope&apos; but found  definitions Message

 

We have checked with IBM on the WSWS3066E error and they of course said that it was a LoadRunner issue.  They said this because we can use a tool called Actional Diagnostics and SOAPUI both successfully.  However, we have LoadRunner and need to test with 200 + Vusers simultaneously.  This is the first time we have attempted to test a web service so I will apologize in advance for my ignorance.

 

Thank you and any assistance would be greatly appreciated.  Doug...

0 Likes
2 Replies
Highlighted
Absent Member.
Absent Member.

Re: LoadRunner 9.5 Web Services Testing

IBM are probably right, the problem here appears to be that the format of the request you are sending is incorrect. This is suggested by the fact you got a 500 response. The additional msg: 'Error: Expected &apos;envelope&apos; but found  definitions' might point to where the issue is.

 

You might want to step back a bit; it helps to gain a good understanding of what you are testing before jumping in. The first thing you should do is to get some example request / response strings and familiarise yourself with them. Not always but usually these will be XML files, they are typiclly sent over HTTP (and for this reason you could use a standard web user to test them, this is desribed here: A useful post).

 

Then you should seek out and sit down with someone who understands how this paritcular service works. Get them to talk you through the communication - any developer / architect worth their salt will be able to guide you in this.

Oliver
0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: LoadRunner 9.5 Web Services Testing

I agree with Oliver. One thing that I do is to perform a network data capture of code that works so that I can see the XML.

 

How are you creating your Web Service script? I have found that importing the WSDL file is usually the best way and working with the application developers to make sure that you have the correct information in the call for successful playback.

 

Since you are getting a 500 error it would appear that your web service call has something that is not correct so the call is failing. Have you looked at the logs on the server where the service is running?

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.