Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Web Services Client Error  RSS feed

 
John Kouch
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
When calling a web service using a web services client using a SOAP binding I am getting the following error. It works fine if I run everything on the same machine. But when I run the web service on a server and run the client on my laptop, it fails. I have researched this and haven't found a workable solution. Can anyone help ?

javascript: x()
banghead

WebServicesFault faultCode: HTTP faultString: ( 404 ) Not Found faultActor: http://IBM-DEF8826A3A3:9080 faultDetail: null: WSWS3192E: Error: return code: ( 404 ) Not Found Error 404: SRVE0200E: Servlet [ws2]: Could not find required servlet class - ws2 . ( 404 ) Not Found at com.ibm.ws.webservices.engine.transport.http.HTTPSender.processStatusCode(HTTPSender.java:546) at com.ibm.ws.webservices.engine.transport.http.HTTPSender.invoke(HTTPSender.java:463) at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:218) at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:274) at com.ibm.ws.webservices.engine.client.Connection.invokeEngine(Connection.java:727) at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:648) at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:609) at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:446) at com.ibm.ws.webservices.engine.client.Stub$Invoke.invoke(Stub.java:732) at com.cf.IdManagerSoapBindingStub.getAllIds(IdManagerSoapBindingStub.java:112) at jk.servlet.IdServlet.processRequest(IdServlet.java:68) at jk.servlet.IdServlet.doGet(IdServlet.java:28) at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1212) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:629) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2837) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:220) at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:204) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1681) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:201) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:103) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:601) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934) at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)
 
Watsh Rajneesh
Ranch Hand
Posts: 110
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Are you using the generated stub mechanism for your webservice client? If so, did you regenerate the stub or _setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY, (String)<webservice endpoint url> ;

My guess is that since your webservice client works if colocated on the same host as the webservice its seemingly because you generated the stub using the wsdl2java compiler tool and the wsdl for your service was using a localhost in the endpoint url (soapbind:address location attribute's value in your wsdl) instead of the domain name for the host where the webservice was located. So please check the wsdl for the service's location attribute value and modify it to mention the fqdn of the server host where your webservice runs and then regenerate the stub and service implementations using the wsdl2java compiler.
 
John Kouch
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the response. I did regenerate the stub. It now appears this may be a server related problem. I was able to run it successfully on one server, but the one I really need it to run on fails. All servers are running WebSphere App Server 6.0. I wonder if there is a WAS server configuration setting that would cause this problem ?
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!