Connection Refused Error in User Guide Sample Client -- regardless of EPR
Hello! We're trying to develop our own small axis web client. We have started by running the client from the user guide. However, it's not cooperating. It seems that it is not even trying to connect to the server yet, since the error message (Connection Refused) is the same regardless of the URL we enter in the EndpointReference targetEPR = new EndpointReference(http://localhost/axis2/services/MyService;) We have downloaded the latest release, 0.94 of AXIS2 as a WAR file and inserted it into Tomcat 5.5.15, which works fine. The WSDL is generated, but directing the Browser itself to the EPR gives us a 500 HTTP error (probably no cause for concern). Therefore we conclude that the error has to be on the client side. We have also followed instructions from other mailing list posts telling us to copy the addressing.mar file to the ~/.axis/modules directory, which didn't change the error message below. Thank you for your time. Regards, -- Chris Sebastian -- - Deploying module : addressing - I/O exception (java.net.ConnectException) caught when processing request: Connection refused - Retrying request - I/O exception (java.net.ConnectException) caught when processing request: Connection refused - Retrying request - I/O exception (java.net.ConnectException) caught when processing request: Connection refused - Retrying request org.apache.axis2.AxisFault: Connection refused; nested exception is: java.net.ConnectException: Connection refused; nested exception is: org.apache.axis2.AxisFault: Connection refused; nested exception is: java.net.ConnectException: Connection refused at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:245) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:449) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:317) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:267) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:393) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:326) at userguide.clients.EchoBlockingClient.main(EchoBlockingClient.java:48) Caused by: org.apache.axis2.AxisFault: Connection refused; nested exception is: java.net.ConnectException: Connection refused at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:290) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:204) ... 6 more Caused by: java.net.ConnectException: Connection refused 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.SocksSocketImpl.connect(SocksSocketImpl.java:364) at java.net.Socket.connect(Socket.java:507) 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:585) at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:139) at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:124) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:100) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:284) ... 7 more
Re: Connection Refused Error in User Guide Sample Client -- regardless of EPR
Try: http://localhost/axis2/listServices When you see your service, it may be listed as faulty. Click on it, and you may see a stack trace. Your 500 error is probably a strong clue. You should also verify the results of listServices shows the Service EPR's as matching what you set on the client. Another option is to turn on logging at the debug level on both the client and server side. Lastly, you could try tcpmon or the soap monitor to see the headers comming in and out - probably not helpful in this case but keep it in mind for future problems. HTH, Robert http://www.braziloutsource.com/ Em Quinta 02 Março 2006 10:55, o Sebastian J. Schultheiss escreveu: Hello! We're trying to develop our own small axis web client. We have started by running the client from the user guide. However, it's not cooperating. It seems that it is not even trying to connect to the server yet, since the error message (Connection Refused) is the same regardless of the URL we enter in the EndpointReference targetEPR = new EndpointReference(http://localhost/axis2/services/MyService;) We have downloaded the latest release, 0.94 of AXIS2 as a WAR file and inserted it into Tomcat 5.5.15, which works fine. The WSDL is generated, but directing the Browser itself to the EPR gives us a 500 HTTP error (probably no cause for concern). Therefore we conclude that the error has to be on the client side. We have also followed instructions from other mailing list posts telling us to copy the addressing.mar file to the ~/.axis/modules directory, which didn't change the error message below. Thank you for your time. Regards, -- Chris Sebastian --
Re: Connection Refused Error in User Guide Sample Client -- regardless of EPR
Try using your port number as in localhost:8080 On Thu, Mar 2, 2006 at 3:55 pm, in message [EMAIL PROTECTED], [EMAIL PROTECTED] wrote: Hello! We're trying to develop our own small axis web client. We have started by running the client from the user guide. However, it's not cooperating. It seems that it is not even trying to connect to the server yet, since the error message (Connection Refused) is the same regardless of the URL we enter in the EndpointReference targetEPR = new EndpointReference(http://localhost/axis2/services/MyService;) We have downloaded the latest release, 0.94 of AXIS2 as a WAR file and inserted it into Tomcat 5.5.15, which works fine. The WSDL is generated, but directing the Browser itself to the EPR gives us a 500 HTTP error (probably no cause for concern). Therefore we conclude that the error has to be on the client side. We have also followed instructions from other mailing list posts telling us to copy the addressing.mar file to the ~/.axis/modules directory, which didn't change the error message below. Thank you for your time. Regards, -- Chris Sebastian NETCB SOLUTIONS (PTY) LTD The Innovation Hub, Enterprise Building, 1st Floor, Unit U19 Lynnwood, Pretoria P.O. Box 14449, Hatfield, Pretoria, 0028 SOUTH AFRICA Tel. +27 12 844 0744 Fax. +27 12 844 0763 NetCB Solutions (Pty) Ltd trading as NetCB.com Reg. 2003/009745/07 Directors: H de Bruin, JC du Toit, LJ Nel, CEO: JP Burgers This message and any attachments relating to official business of NetCB Solutions (Pty) Ltd (NETCB) is proprietary to NETCB and intended for the original addressee only. The message may contain information that is confidential and subject to legal privilege. Any views expressed in this message are those of the individual sender. If you have received this message in error, please notify the original sender immediately and destroy the original message. If you are not the intended recipient of this message, you are hereby notified that you must not disseminate, copy, use, distribute, or take any action in connection therewith. NETCB cannot ensure that the integrity of this communication has been maintained nor that it is free of errors, viruses, interception and/or interference. NETCB is not liable whatsoever for loss or damage resulting from the opening of this message and/or attachments and/or the use of the information contained in this message and/or attachments.
Re: Connection Refused Error in User Guide Sample Client -- regardless of EPR
Hi Robert, thanks for your fast reply. Our problem is solved now, but it wasn't due to a faulty service. The following is only for users having the same error message: We had changed the port to 80 on the local machine (tunneling) and recompiled the source (That's why we didn't use localhost:8080, as Habib suggested). Then we noticed that the .sh or .bat files of the example actually call the class files stored in the .jar and not the ones in the directories (maybe that's a java setting?) After we fixed that, the test went through ok, both under Linux and Windows, on the host where the server runs and on a remote machine. Thanks for your help! -- Sebi When you see your service, it may be listed as faulty. Click on it, and you may see a stack trace. Your 500 error is probably a strong clue. You should also verify the results of listServices shows the Service EPR's as matching what you set on the client. Another option is to turn on logging at the debug level on both the client and server side. Lastly, you could try tcpmon or the soap monitor to see the headers comming in and out - probably not helpful in this case but keep it in mind for future problems. HTH, Robert http://www.braziloutsource.com/ Em Quinta 02 Março 2006 10:55, o Sebastian J. Schultheiss escreveu: Hello! We're trying to develop our own small axis web client. We have started by running the client from the user guide. However, it's not cooperating. It seems that it is not even trying to connect to the server yet, since the error message (Connection Refused) is the same regardless of the URL we enter in the EndpointReference targetEPR = new EndpointReference(http://localhost/axis2/services/MyService;) We have downloaded the latest release, 0.94 of AXIS2 as a WAR file and inserted it into Tomcat 5.5.15, which works fine. The WSDL is generated, but directing the Browser itself to the EPR gives us a 500 HTTP error (probably no cause for concern). Therefore we conclude that the error has to be on the client side. We have also followed instructions from other mailing list posts telling us to copy the addressing.mar file to the ~/.axis/modules directory, which didn't change the error message below. Thank you for your time. Regards, -- Chris Sebastian
