Quantcast
Channel: All LoadRunner Practitioners Forum posts
Viewing all articles
Browse latest Browse all 12134

Re: Problem with Web Services

$
0
0

Hello Phuong Nguyen, thanks for answering.

 

This is the extended log:

 

Starting action Action.
Action.c(3): Web service call "obtenerRequerimiento_101" started
Action.c(3): "Content-Type: application/soap+xml; charset=UTF-8" header registered for adding to requests from the immediately following Action function  	[MsgId: MMSG-26506]
Action.c(3): "Accept: application/soap+xml, application/dime, multipart/related, text/*" header registered for adding to requests from the immediately following Action function  	[MsgId: MMSG-26506]
Action.c(3): "User-Agent: Axis/1.3" header registered for adding to requests from the immediately following Action function  	[MsgId: MMSG-26506]
Action.c(3): "SOAPAction: http://URL/ejecucion/requerimiento/servicio/1/0/obtenerRequerimiento/" header registered for adding to requests from the immediately following Action function  	[MsgId: MMSG-26506]
Action.c(3): "Cache-Control: no-cache" header registered for adding to requests from the immediately following Action function  	[MsgId: MMSG-26506]
Action.c(3): "Pragma: no-cache" header registered for adding to requests from the immediately following Action function  	[MsgId: MMSG-26506]
Action.c(3): t=1555ms: Connecting [0] to host 192.1.10.34:8080  	[MsgId: MMSG-26000]
Action.c(3): t=1558ms: Connected socket [0] from 10.10.10.32:3373 to 192.1.10.34:8080 in 2 ms  	[MsgId: MMSG-26000]
Action.c(3): t=1558ms: 192-byte request headers for "https://URL/ejecucion/requerimiento/Requerimiento_1_0" (RelFrameId=1, Internal ID=1)
Action.c(3):     CONNECT URL:443 HTTP/1.0\r\n
Action.c(3):     User-Agent: Mozilla/4.0 (compatible; MSIE 4.0; Windows NT)\r\n
Action.c(3):     Host: URL\r\n
Action.c(3):     Proxy-Connection: Keep-Alive\r\n
Action.c(3):     Content-Length: 0\r\n
Action.c(3):     Pragma: No-Cache\r\n
Action.c(3):     \r\n
Action.c(3): t=1565ms: 400-byte response headers for "https://URL/ejecucion/requerimiento/Requerimiento_1_0" (RelFrameId=1, Internal ID=1)
Action.c(3):     HTTP/1.1 407 Proxy Authentication Required ( The ISA Server requires authorization to fulf
Action.c(3):     ill the request. Access to the Web Proxy filter is denied.  )\r\n
Action.c(3):     Via: 1.1 SRVTEAING02\r\n
Action.c(3):     Proxy-Authenticate: Negotiate\r\n
Action.c(3):     Proxy-Authenticate: Kerberos\r\n
Action.c(3):     Proxy-Authenticate: NTLM\r\n
Action.c(3):     Connection: close\r\n
Action.c(3):     Proxy-Connection: close\r\n
Action.c(3):     Pragma: no-cache\r\n
Action.c(3):     Cache-Control: no-cache\r\n
Action.c(3):     Content-Type: text/html\r\n
Action.c(3):     Content-Length: 723   \r\n
Action.c(3):     \r\n
Action.c(3): t=1575ms: 124-byte response body for "https://URL/ejecucion/requerimiento/Requerimiento_1_0" (RelFrameId=1, Internal ID=1)
Action.c(3):     <HTML><HEAD><TITLE>Error Message</TITLE>\r\n
Action.c(3):     <META http-equiv=Content-Type content="text/html; charset=windows-1252">\r\n
Action.c(3):     <BODY>\r\n
Action.c(3): t=1575ms: 599-byte response body for "https://URL/ejecucion/requerimiento/Requerimiento_1_0" (RelFrameId=1, Internal ID=1)
Action.c(3):     <TABLE><TR><TD id=L_dt_1><B>Network Access Message: The page cannot be displayed<B></TR></
Action.c(3):     TABLE>\r\n
Action.c(3):     <TABLE><TR><TD height=15></TD></TR></TABLE>\r\n
Action.c(3):     <TABLE>\r\n
Action.c(3):     <TR><TD id=L_dt_2>Technical Information (for Support personnel)\r\n
Action.c(3):     <UL>\r\n
Action.c(3):     <LI id=L_dt_3>Error Code: 407 Proxy Authentication Required. The ISA Server requires autho
Action.c(3):     rization to fulfill the request. Access to the Web Proxy filter is denied. (12209)\r\n
Action.c(3):     <LI id=L_dt_4>IP Address: 192.1.10.34\r\n
Action.c(3):     <LI id=L_dt_5>Date: 3/19/2014 1:21:54 PM [GMT]\r\n
Action.c(3):     <LI id=L_dt_6>Server: URL.local\r\n
Action.c(3):     <LI id=L_dt_7>Source: proxy\r\n
Action.c(3):     </UL></TD></TR></TABLE></BODY></HTML>\r\n
Action.c(3): t=1578ms: Closing connection [0] to server 192.1.10.34 - proxy indicated that the connection should be closed  	[MsgId: MMSG-26000]
Action.c(3): t=1578ms: Closed connection [0] to 192.1.10.34:8080 after completing 1 request  	[MsgId: MMSG-26000]
Action.c(3): Error:InvokeMethod failed: Internal Error - connection to "URL" is closed in state STATE_DONE
Action.c(3): InvokeMethod trace: com.mercury.ws.exception.ProxyInvocationException: Soap Fault Occured
	at com.mercury.ws.invoker.JInvoker$JMethodInvoker.invoke(JInvoker.java:2774)
	at com.mercury.ws.invoker.JInvoker.invoke(JInvoker.java:288)
Caused by: org.xml.sax.SAXException: Bad envelope tag:  HTML
	at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
	at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:701)
	at org.apache.axis.Message.getSOAPEnvelope(Message.java:436)
	at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:60)
	at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
	at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
	at org.apache.axis.client.Call.invoke(Call.java:2767)
	at org.apache.axis.client.Call.invoke(Call.java:2443)
	at org.apache.axis.client.Call.invoke(Call.java:2366)
	at org.apache.axis.client.Call.invoke(Call.java:1812)
	at URL.ejecucion.requerimiento.servicio._1._0.RequerimientoBindingStub.obtenerRequerimiento(RequerimientoBindingStub.java:878)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at com.mercury.ws.invoker.JInvoker$JMethodInvoker.invoke(JInvoker.java:2767)
	... 1 more
Caused by: org.xml.sax.SAXException: Bad envelope tag:  HTML
	at org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuilder.java:71)
	at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048)
	at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
	at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
	at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
	at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
	at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
	at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
	at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
	at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
	... 15 more
Action.c(3): Error:InvokeMethod failure: AXIS engine threw an exception.
Action.c(3): Error:Internal error, please call customer support. Details: Error while retrieving body -- can not parse output parameters
Action.c(3): Error:Web service call "obtenerRequerimiento_101" execution failed
Ending action Action.

 It shows a problem with the proxy: "Action.c(3): t=1578ms: Closing connection [0] to server 192.1.10.34 - proxy indicated that the connection should be closed".However i configured the proxy when i imported the WSDL.

 

About "mustUnderstand", no, we aren't using that parameter. The WS manager is working in the policy about asking the header and the security (that's what they told me or something like that). The "UsernameToken" is required.

 

Regards.


Viewing all articles
Browse latest Browse all 12134

Trending Articles