• Post Reply Bookmark Topic Watch Topic
  • New Topic

Problem with Websphere Application Server

 
Nagaraju Nookala
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

I am new to Webservices. I created a webservice with WSDK5.1 and published successfully. I wanted to run my service on Websphere Application Server 5.1. I modified the wsdl files manually by changing the port address from 6080 to 9080 and recreated the .ear file and deployed it on to the Application Server. When I am accessing the service on the AppServer I am getting the following error:

[7/27/04 14:46:17:234 EDT] 3c6614bb enterprise I com.ibm.ws.webservices.engine.enterprise TRAS0014I: The following exception was logged WebServicesFault
faultCode: Server.generalException
faultString: java.net.ConnectException: Connection refused: connect
faultActor: null
faultDetail:

java.net.ConnectException: Connection refused: connect
at com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServicesFault.java:150)
at com.ibm.ws.webservices.engine.transport.http.HTTPSender.invoke(HTTPSender.java:200)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:212)
at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:253)
at com.ibm.ws.webservices.engine.client.Connection.invokeEngine(Connection.java:686)
at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:610)
at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:440)
at com.ibm.ws.webservices.engine.client.Stub$Invoke.invoke(Stub.java:659)
at com.pemsservice.SimpleDBAccessSoapBindingStub.getUserName(SimpleDBAccessSoapBindingStub.java:79)
at org.apache.jsp._Result._jspService(_Result.java:261)
at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:344)
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:662)
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:974)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:555)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:119)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:618)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:443)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:329)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:194)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:181)
at java.net.Socket.connect(Socket.java:459)
at java.net.Socket.connect(Socket.java:409)
at java.net.Socket.<init>(Socket.java:315)
at java.net.Socket.<init>(Socket.java:143)
at com.ibm.ws.webservices.engine.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:145)
at com.ibm.ws.webservices.engine.transport.http.HTTPSender$1.run(HTTPSender.java:240)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:111)
at com.ibm.ws.webservices.engine.transport.http.HTTPSender.getSocket(HTTPSender.java:237)
at com.ibm.ws.webservices.engine.transport.http.HTTPSender.invoke(HTTPSender.java:154)
... 33 more

One interesting thing is that if the AppServer that is embedded in wsdk is also running, I am not getting the above exception(eventhough I am accessing the service that is running on port 9080). Please help me. Thanks in advance.

-Nagaraju.
 
Sandeep Bhagavatula
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Looks like you are not able to connect to the server at all. The exception is coming on the client side. That means that the Proxy that you use to invoke the call has wrong url. Correct that and you should be fine
Sandeep Bhagavatula
 
Nagaraju Nookala
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the quick reply. But, I didn't get what you were trying to say. Sorry, I am at the very beginning of webservices. I have the below listed files that were created by wsdk51.

PemsWebService/JavaSource/com/pemsservice
SimpleDBAccess_SEI.java

PemsWebService\WebContent\WEB-INF
ibm-web-bnd.xmi
ibm-web-ext.xmi
ibm-webservices-bnd.xmi
ibm-webservices-ext.xmi
SimpleDBAccess_mapping.xml
web.xml
webservices.xml

PemsWebService\WebContent\WEB-INF\wsdl
SimpleDBAccess.wsdl

PemsWebServiceClient\JavaSource\com\pemsservice
SimpleDBAccess.java
SimpleDBAccessService.java
SimpleDBAccessServiceLocator.java
SimpleDBAccessSoapBindingStub.java

PemsWebServiceClient\WebContent\sample\SimpleDBAccess
Input.jsp
Method.jsp
Result.jsp
TestClient.jsp

PemsWebServiceClient\WebContent\WEB-INF\wsdl
SimpleDBAccess.wsdl

For the bean I wrote in the following dir with the name specified below:
PemsWebService/JavaSource/com/pemsservice
SimpleDBAccess.java

If you can tell me what are the source files that I got to look into and modify, that will be a great help. I am sorry for troubling you. Thank you very much.

Nagaraju.
 
Sandeep Bhagavatula
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In your SimpleDBAccessServiceLocator.java there should be a String url. Just change the port number there
 
Nagaraju Nookala
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you very much, Sandeep. It worked.
 
Che Cheun
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, I have got the similar problem
" faultString: java.net.ConnectException: Connection refused: connect"

I use the SDAQProviderServiceLocator.class as a input jar, its URL is
http://localhost:9080/sdap/services/SDAQServices and cannot be edited.

my test client code is under a package named "test" under a java project named "Test".

How can I solve the connect problem?

Thanks,
Che
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!