Error in consuming a WSDl client through a servlet

Hi Guys,
I have generated a client by consumig an enterprise service wsdl.
I have made a servlet to call the client but i get the error as shown below..
Request your help ASAP.
"Application error occurred during the request procession."
Details: Exception:
javax.servlet.ServletException: javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at test.TestServlet.doGet(TestServlet.java:66)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:137)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
Caused by: javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
 at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
 at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
 at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
 at test.TestServlet.doGet(TestServlet.java:51)
 ... 30 more
Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
 ... 38 more
Caused by: java.net.ConnectException: Connection timed out: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 at java.net.Socket.connect(Socket.java:519)
 at java.net.Socket.connect(Socket.java:469)
 at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
 at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
 at sun.net.www.http.HttpClient.New(HttpClient.java:304)
 at sun.net.www.http.HttpClient.New(HttpClient.java:316)
 at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
 at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
 at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
 at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
 ... 39 more
 Root cause:
javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
 at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
 at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
 at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
 at test.TestServlet.doGet(TestServlet.java:51)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:137)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
 ... 38 more
Caused by: java.net.ConnectException: Connection timed out: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 at java.net.Socket.connect(Socket.java:519)
 at java.net.Socket.connect(Socket.java:469)
 at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
 at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
 at sun.net.www.http.HttpClient.New(HttpClient.java:304)
 at sun.net.www.http.HttpClient.New(HttpClient.java:316)
 at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
 at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
 at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
 at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
 ... 39 more
javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
 at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
 at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
 at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
 at test.TestServlet.doGet(TestServlet.java:51)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:137)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
 ... 38 more
Caused by: java.net.ConnectException: Connection timed out: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 at java.net.Socket.connect(Socket.java:519)
 at java.net.Socket.connect(Socket.java:469)
 at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
 at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
 at sun.net.www.http.HttpClient.New(HttpClient.java:304)
 at sun.net.www.http.HttpClient.New(HttpClient.java:316)
 at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
 at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
 at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
 at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
 ... 39 more

Similar Messages

Error in Consuming external WSDL in ABAP

Dear Gurus,
I am trying to consume a WSDL in ABAP using enterprise services in SE80. After load the WSDL and making logical port, when i test the WSDL, it gives an error : (SOAP:1.008 SRT: Couldn't create Object: ("ICF Error when creating HTTP client object by Config for U )
Can any body tells what is the cause of this error? I tried but unable to resolve the problem. Help from integration and ABAP gurus is required. Thanks

Hello Imran,
Have you tried, or is it practicable for your situation, to create the consumer service and the logical port using the URL directly, instead of a local file? (as you have shown in your print, it looks to me that it's local file)
Maybe you can check if this WS has been used normally by other consumers, or even test it with SoapUI to guarantee it is functional (also to compare the requests). You could put this WSDL under a validation tool, i know that SAP does it when the WSDL is under processing, and it goes wrong when some elements/attributes aren't supported ... and i see you could upload it successfully, but despite of it is good to double check.
Good luck!
Renan

Error While Consuming Public Web Service through Stand Alone Proxy

Hi,
I am getting the below error when I am consuming a public web service through Stand Alone Proxy.
java.rmi.RemoteException: Service call exception; nested exception is:
     com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (407) Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy filter is denied. ).
     at com.mindtree.examples.GlobalWeatherSoapStub.getCitiesByCountry(GlobalWeatherSoapStub.java:159)
     at com.mindtree.examples.GlobalWeatherSoapStub.getCitiesByCountry(GlobalWeatherSoapStub.java:168)
     at com.mindtree.examples.WebServiceClient.main(WebServiceClient.java:18)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (407) Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy filter is denied. ).
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:903)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1346)
     at com.mindtree.examples.GlobalWeatherSoapStub.getCitiesByCountry(GlobalWeatherSoapStub.java:152)
     ... 2 more
Regards,
Venkatesh

Hi,
I am still facing the same issue.
Regards,
Venkatesh

Error while consuming external WSDL file

Hi,
I have created the client proxy for the WSDL file(i.e. .Net webservice's WSDL file). While creating the logical port it is giving the error,
'Error: Uninstantiated object "subject sidl service" in method IF_SRT_WSP_CONFIG_SIDL~CREATE_CLNT_CFG_FROM_WSDL_D of class CL_SRT_WSP_CONFIG_SIDL '. Please help to solve this problem.

Hi,
Thanks. I checked with program you have given, while executing it is displaing the WSDL file as inconsisten value as follows,
<sidl:DEFINITION xmlns:sidl="http://xml.sap.com/2006/08/esi/sidl/dump">
<sidl:consistencyCheck>Incorrect value:</sidl:consistencyCheck>
- <sidl:registry assigned="true">
- <sidl:entityContainer>
- <sidl:documentNamespace namespace="http://schemas.xmlsoap.org/wsdl/">
<sidl:entity targetNamespace="http://tempuri.org/" location="http://tedweb2k3.wipro.com/PublishCopy/TTWis/tt.asmx?wsdl" />
</sidl:documentNamespace>
- <sidl:documentNamespace namespace="http://www.w3.org/2001/XMLSchema">
<sidl:entity targetNamespace="http://www.w3.org/2001/XMLSchema" location="" />
<sidl:entity targetNamespace="http://tempuri.org/" location="" />
</sidl:documentNamespace>
</sidl:entityContainer>
</sidl:registry>
Please help me in this regard.

Error while consuming a webservice in nwds

Dear Users,
I m facing an error while consuming a wsdl webservice in webdynpro java error................
Error Mon Apr 20 16:53:29 IST 2009 Apr 20, 2009 4:53:29 PM          com.sap.ide.webdynpro.ui.service.ServicesUI          [Thread[ModalContext,5,main]] Error: Internal error
   Plugin name: Web Dynpro Model Editor Services
   Plugin ID : com.sap.ide.webdynpro.service.modeleditor
   Class      : com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelWizard$9
   Method     : doImportWebServiceModel
   Message    : Web Service model import failed
   Exception : com.sap.ide.ws.proxygenerator.ProxyGeneratorException: Problems while generating the Proxy Definition!
com.sap.ide.ws.proxygenerator.ProxyGeneratorException: Problems while generating the Proxy Definition!
     at com.sap.ide.ws.proxygenerator.ProxyGeneratorWrapper.generateProxy(ProxyGeneratorWrapper.java:416)
     at com.sap.ide.ws.proxygenerator.ProxyGeneratorWrapper.generateStandAlone(ProxyGeneratorWrapper.java:283)
     at com.sap.ide.ws.proxygenerator.ProxyGeneratorWrapper.generateStandAlone(ProxyGeneratorWrapper.java:279)
     at com.sap.ide.metamodel.importers.webservice.GenerateWS.doGenerate(GenerateWS.java:92)
     at com.sap.ide.metamodel.importers.webservice.WebServiceModelImporter.doImport(WebServiceModelImporter.java:117)
     at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelWizard$9.run(ModelWizard.java:1155)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
-- caused by --
com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Problem with WSDL file parsing. See nested message.
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:182)
     at com.sap.ide.ws.proxygenerator.InternalHelperFunctions.generateInterfaces(InternalHelperFunctions.java:370)
     at com.sap.ide.ws.proxygenerator.ProxyGeneratorWrapper.generateProxy(ProxyGeneratorWrapper.java:372)
     at com.sap.ide.ws.proxygenerator.ProxyGeneratorWrapper.generateStandAlone(ProxyGeneratorWrapper.java:283)
     at com.sap.ide.ws.proxygenerator.ProxyGeneratorWrapper.generateStandAlone(ProxyGeneratorWrapper.java:279)
     at com.sap.ide.metamodel.importers.webservice.GenerateWS.doGenerate(GenerateWS.java:92)
     at com.sap.ide.metamodel.importers.webservice.WebServiceModelImporter.doImport(WebServiceModelImporter.java:117)
     at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelWizard$9.run(ModelWizard.java:1155)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
Caused by: com.sap.engine.lib.xml.util.NestedException: IO Exception occurred while parsing file:Server redirected too many times (20) -> java.net.ProtocolException: Server redirected too many times (20)
     at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1039)
     at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1126)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:178)
     ... 8 more
Caused by: java.net.ProtocolException: Server redirected too many times (20)
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:823)
     at java.net.URL.openStream(URL.java:913)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:201)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:263)
     at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
     at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
     at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
     at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
     at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1025)
     ... 10 more
Please help me in solving his issue.
regards,
Sathya

I have the same issue attempting to connect my application to this WSDL:
http://erp.esworkplace.sap.com/sap/bc/srt/xip/sap/ecc_projwbselmntcancrc?sap-client=800&wsdl=1.1&mode=sap_wsdl
I can load the WSDL fine as an XML file. I can also load the WSDL fine if I connect via Firefox or a browser. I can open it fine in SoapUI. I just can't access it from my Java application.
2009-10-26 18:11:45,943 ERROR [com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext] Loading of definition failed for [http://uid:password-erp.esworkplace.sap.com/sap/bc/srt/xip/sap/ecc_projwbselmntcancrc?sap-client=800&wsdl=1.1&mode=sap_wsdl]; java.net.ProtocolException: Server redirected too many times (20)
2009-10-26 18:11:45,943 ERROR [com.eviware.soapui.SoapUI] An error occured [Server redirected too many times (20)], see error log for details
2009-10-26 18:11:45,943 ERROR [soapui.errorlog] java.net.ProtocolException: Server redirected too many times (20)
java.net.ProtocolException: Server redirected too many times (20)
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
     at java.net.URL.openStream(Unknown Source)
     at com.adobe.idp.dsc.webservice.MyWsdlLoader.load(WebServiceSoapUIInvoker.java:675)
     at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:106)
     at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:469)
     at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:460)
     at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.cacheWsdl(WsdlLoader.java:176)
     at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext$Loader.construct(WsdlContext.java:207)
     at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:45)
     at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:111)
     at java.lang.Thread.run(Unknown Source)
2009-10-26 18:11:45,943 ERROR [STDERR] java.net.ProtocolException: Server redirected too many times (20)
2009-10-26 18:11:45,943 ERROR [STDERR]      at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
2009-10-26 18:11:45,943 ERROR [STDERR]      at java.net.URL.openStream(Unknown Source)
2009-10-26 18:11:45,943 ERROR [STDERR]      at com.adobe.idp.dsc.webservice.MyWsdlLoader.load(WebServiceSoapUIInvoker.java:675)
2009-10-26 18:11:45,943 ERROR [STDERR]      at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:106)
2009-10-26 18:11:45,943 ERROR [STDERR]      at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:469)
2009-10-26 18:11:45,943 ERROR [STDERR]      at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:460)
2009-10-26 18:11:45,943 ERROR [STDERR]      at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.cacheWsdl(WsdlLoader.java:176)
2009-10-26 18:11:45,943 ERROR [STDERR]      at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext$Loader.construct(WsdlContext.java:207)
2009-10-26 18:11:45,943 ERROR [STDERR]      at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:45)
2009-10-26 18:11:45,943 ERROR [STDERR]      at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:111)
2009-10-26 18:11:45,943 ERROR [STDERR]      at java.lang.Thread.run(Unknown Source)
Any ideas?
Edited by: tburke on Oct 27, 2009 2:26 AM

Error target namespace must be absolute URI when consuming external WSDL

Hi,
I'm trying to consume external WSDL which has relative target namespace.
Through SE80 transaction I select Create -> Enterprise Server -> Service Consumer.
I have tried with URL and local file options but the result is the following in both cases:
At the en of the wizard I receive the errors "exception in Error-Handler" and "Error target namespace must be absolute URI".
I'm on ECC 6.0 SP 18.
Anybody knows how to solve this problem? Maybe is not possible to consume external WSDL with relative URI?
Thanks
Regards

Hi,
I think the problem is that the WSDL is not WS-I compliant.
I have found note 1327511 (Limiations and common problems in ABAP WSDL processing) and with the report RSSIDL_DESERIALIZE_DEMOI have found the same error.
Anybody can confirm this?
Is there any other document or reference where SAP indicates this fact?
Thanks
Regards

Error while consuming Odata service from Gateway client i.e /iwfnd/gw_client

Hello Experts.
I am facing below an error while consuming the Odata service from GW client... The error is "No service found for the namespace /IWFND/,name ZTEST_STOREROOM_SRV,version 001". Even i have tried to deep dive in /IWFND/Error_log but no use..
Actually what I was doing :- My aim is to connect multiple back end systems in the same server with the help of Aliasing concept.. I have created multiple aliases and added in the /IWFND/MAINT_Service transaction.. but i am not getting how to consume the service..
I have followed the solution upto some extent in the link => Multiple Origin Composition - SAP NetWeaver Gateway Foundation (SAP_GWFND) - SAP Library
Can you please let me know how to resolve this.. Also please let me know, the syntax for the URI...
Your help is highly appreciated..
Please find the screenshot attached.
Thanks,
Srinivas.

Hello @Nrisimhanadh_Yandamuri
Thanks for your reply..
I have got all the required authorization.. But still I am not able to hit the service.. Please let me know what could be the solution..
Thanks,
Srinivas.

Error installing MBAM client through SCCM task sequence error code 80070005

Hi
I'm getting a weird error when trying to deploy the MBAM 2.0 client through a task sequence, it was working but now keep seeing the below two errors in the AppEnforce log, after it has returned the 3010 soft reboot code.
CoCreateInstance failed on CLSID_ProductSrcUpdateMgr, error 80070005
Failed to update msi source list, error 0x80070005
does anyone have any idea what these mean?
thanks
Mark

What is the silent installation command line for MBAM client you are using. I would suggest to first test the silent installation manually and test whether it is working successfully or not.
Are you using the msi installer or the setup.exe
Command Line for Deploying the MBAM 2.0 Client
MBAMClientSetup.exe /q
Gaurav Ranjan

Consuming odsi services exposed through osb

I've followed these procedures:
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/dsptransport/
Now, as the web service client needs to call the data service more than once inside the same transaction, that is, I need to propagate the transactional context, I changed the proxy service to have SB Transport (instead of http).
The diagram would be:
ws client <--> [ (PS1, sb transport) -- (BS1, dsp transport)] -- [ODSI] -- [Data Sources]
Is this use case supported?
I tried to consume the data service (through PS1) using the mediator API (exported from ODSI) and got the following error, after changing the transport type of PS1 (from http to sb).
Caused by: java.net.MalformedURLException: unknown protocol: sb
 at java.net.URL.<init>(URL.java:574)
 at weblogic.wsee.connection.transport.http.HTTPClientTransport.connect(HTTPClientTransport.java:109)
 at weblogic.wsee.connection.soap.SoapClientConnection.send(SoapClientConnection.java:55)
 at com.bea.dsp.das.ws.WSConnection.sendRequest(WSConnection.java:202)
 ... 39 more
I looked for a way to try to set the client transport type in the ODSI API with no success.
Thank you in advance,
Alexandre

1) You're using the ODSI ws client to call an sb protocol proxy service. That doesn't work. The ODSI ws client only knows how to call ODSI webservices (or webservices that look like ODSI web services).
2) You would make your life a lot easier if you simple combined whatever you need done in your multiple calls to ODSI into a single data service. But you don't need to.
3) In your picture, it's not clear if the multiple calls to ODSI are done within the same proxy-service call, or if multiple client calls are required. If they are in the same proxy-service call, then all you need is your proxy-service to manage the transaction (an OSB person should be able to tell you how to get that - perhaps it is the default). If your proxy-service is managing the transaction, then it doesn't matter how that proxy-service is being called. But if it requires multiple client calls, then the client has to manage the transaction.

XML Parser Error while creating Web service Client using JAX RPC

hello evryone,
Im facing XML Parser Error while creating web service client using JAX RPC. Im using Net Beans IDE for development purpose. I have wrote configuration file for client. Now i want to create Client stub. However i dont know how to do this in Net Beans. So i tried to do it from Command promt using command :
wscompile -gen:client -d build -classpath build config-wsdl.xml
here im getting Error:
error parsing configuration file: XML parsing error: com.sun.xml.rpc.sp.ParseException:10: XML declaration may only begin entities
Please help me out.
Many thanks in advance,
Kacee

Can i use the client generated using jdeveloper 11g to import into the oracle forms 10g, i.e., form builder 10g. Currently this is the version we have in our office.

Error in loading the WSDL file

hi
when i am creating a Adaptive Webservice model with the sneak preview 2004s
while Choosing the published service from UDDI
i am getting and error called
"Error in loading the WSDL file"
i have gone through the log files it basically saying that
Caused by: java.io.IOException: Cannot connect to http://192.168.1.69:50100/QuickCarRentalService/Config1?wsdl, passing via http proxy: :80: Connection refused: connect
but i am not using any proxy server
what all changes i need to do in proxy server settings
Regards
JM

Hi John,
For changing the Proxy Settings in NWDS.
Navigate to Window --> Preferences.
Under Work Bench, Select Proxy Settings.
There is a Check box saying "Use Proxy Sever", uncheck this one;
and try imprting you WSDL file again.
Hope it helps.
Regards,
Alka.

Error while consuming CAF Web Service in ABAP

Hi experts,
I need to consume a CAF Web Service in ABAP 7.0. While trying to generate the Proxy Object in SE80 it is thowing an error "Proxy generation terminated: WSDL error. (<extension> not supported)" and terminating the Proxy generation.
Can anyone please help me out with the solution for this?
Thanks in Advance.
Vaishali.

Hi,
waiting for reply.....

401 Unauthorized:HTTP transport error while calling external WSDL from BPEL

Hi,
I have simple BPEL process whic calls siebel WSDL file through partner link.
I have successfully compiled and deployed BPEL process, when i initiate the Process, instace got errored out at invoke activity.
Error Goes like this
"<remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>
exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException:
java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 401 Unauthorized</summary>
</part></remoteFault>"
Can anybody help on this issue, Could you please give me possible solution.
Thank youl.

we have not provided any authentication credentials to XMLSpy, we have just uploaded siebel WSDL file then sent the SOAP request with some customer Id then we have received proper response with all desired customer data.
In the same way we tried to call same siebel WSDL file from BPEL process throgh partner link. errored instance has created with 401 unauthorised HTTP transport error..
Do you think is this probem at siebel application side?
We have deployed our BPEL process to SOA server which is having HTTP port 7777.
as per my investigation,i found that we have to open port from siebel side (which WSDL file we are calling) which matches with above HTTP port number.
Do you have any idea on this above clue? Please let us know more details on this.

Getting error in consuming google webservices from JspDynPage

Hi All,
Getting following error while consuming google webservices from JspDynPage
An exception occurred while processing a request for :
iView : GoogleSer.google
Component Name : GoogleSer.google
Could not find portal application com.company.global.enterprise.portal.wsdl.webservices.service.
Code :
MyGoogle googleService =
(MyGoogle) PortalRuntime.getRuntimeResources().getService("com.company.global.enterprise.portal.wsdl.webservices.service.MyGoogle");
GoogleSearchResult result = googleService.doGoogleSearch("google", "SAP", 0, 10, false, "", false, "", "", "");
ResultElement[] results = result.getResultElements();
if(results != null) {
response.write(" Search Result Size " +results.length );
for (int i = 0; i < results.length; i++) {
response.write((i + 1) + ": " + results);
Thanks
Rudra

Hi,
I am still having the same problem, however the scenario in which I am getting varies.
I am getting this exception:
"com.sap.engine.services.webservices.jaxm.soap.accessor.NestedSOAPException: IOError while working with the message."
Some users when trying to login into the portal are getting blank screen and for some the portal launcher page is loading fine and could go to the Home Page.
When I view the logs I am seeing the Nested Soap Exception.
Any Ideas??? Starting the J2EE engine also did'nt help.
Thanks in advance.
Madhavi

Error when creating web service client in netbeans

i tried to create a web service client from a wsdl and an error pops up:
web service client can not be created by jaxws:wsimport utility.
reason: com.sun.tools.xjc.api.schemacompiler.resetschema()v
There might be a problem during java artifacts creation: for example a name conflict in generated classes.
To detect the problem see also the error messages in output window.
You may be able to fix the problem in WSDL Customization dialog
(Edit Web Service Attributes action)
or by manual editing of the local wsdl or schema files, using the JAXB customization
(local wsdl and schema files are located in xml-resources directory).
end of error message
I am using netbeans 6.0 RC 2 and the bundled tomcat 6.0.13. Please help me.

Hi Yatan
The error is mostly there may be some Duplicate variable/schema element decalared in the wsdl or the xsd referred in the wsdl. Like in WSDL for any Operations, most of the times, we use input and outputs as complex xsd element. We declare these xsd in the same file or in another file and import that in the .wsdl file. So check or validate your XSD file for any Duplicates.
In JDeveloper itself, I think, you can open XSD or WSDL and validate it from right click menu options like that.
Thanks
Ravi Jegga

Error in consuming a WSDl client through a servlet

Similar Messages

Maybe you are looking for