"No route to host" typically means that the host is being connected to without using a proxy, and the firewall is blocking the connection attempt. How does your app determine their is a proxy?
On 4 Jun 2003 at 12:18, Malte Kempff wrote: > Hello > > there are some for me not understandeble Problems with Connections to the > Host via Apache Soap while using Proxies. > The application is a Java-Web-Start-Application. Everything is working with > the given Proxy, the bowser, the receiving of > the application via Java-Web-Start. But trying to make a soap-call ends in a > exceptions like this, allthough the proxy-address was given. > > [SOAPException: faultCode=SOAP-ENV:Client; msg=Error connecting to > 62.159.233.111:80: java.net.NoRouteToHostException: No route to host: > connect; targetException=java.net.NoRouteToHostException: No route to host: > connect] > at org.apache.soap.util.net.HTTPUtils.getSocket(Unknown Source) > at org.apache.soap.util.net.HTTPUtils.post(Unknown Source) > at org.apache.soap.util.net.HTTPUtils.post(Unknown Source) > at org.apache.soap.transport.http.SOAPHTTPConnection.send(Unknown Source) > at org.apache.soap.rpc.Call.invoke(Unknown Source) > at org.apache.soap.rpc.Call.invoke(Unknown Source) > at > de.mc.etnbestterm.data.SoapCallingDataHolder.callSoaply(SoapCallingDataHolde > r.java:75) > at > de.mc.etnbestterm.data.MainDataHolder.connectServerToDB(MainDataHolder.java: > 457) > at de.mc.etnbestterm.data.MainDataHolder.<init>(MainDataHolder.java:61) > at > de.mc.etnbestterm.data.SingletonManager.getMainDataHolder(SingletonManager.j > ava:46) > at de.mc.etnbestterm.gui.WillkommenPanel.jbInit(WillkommenPanel.java:62) > at de.mc.etnbestterm.gui.WillkommenPanel.<init>(WillkommenPanel.java:52) > at de.mc.etnbestterm.gui.MainFrame.<init>(MainFrame.java:40) > at de.mc.etnbestterm.Bestellterminal.jbInit(Bestellterminal.java:64) > at de.mc.etnbestterm.Bestellterminal.<init>(Bestellterminal.java:44) > at de.mc.etnbestterm.Bestellterminal.main(Bestellterminal.java:117) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at com.sun.javaws.Launcher.executeApplication(Unknown Source) > at com.sun.javaws.Launcher.executeMainClass(Unknown Source) > at com.sun.javaws.Launcher.continueLaunch(Unknown Source) > at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source) > at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source) > at com.sun.javaws.Launcher.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > Caused by: java.net.NoRouteToHostException: No route to host: connect > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.PlainSocketImpl.doConnect(Unknown Source) > at java.net.PlainSocketImpl.connectToAddress(Unknown Source) > at java.net.PlainSocketImpl.connect(Unknown Source) > at java.net.Socket.connect(Unknown Source) > at java.net.Socket.connect(Unknown Source) > at java.net.Socket.<init>(Unknown Source) > at java.net.Socket.<init>(Unknown Source) > at org.apache.soap.util.net.SocketUtils.createSocket(Unknown Source) > at org.apache.soap.util.net.HTTPUtils.getSocket(Unknown Source) > at org.apache.soap.util.net.HTTPUtils.post(Unknown Source) > at org.apache.soap.util.net.HTTPUtils.post(Unknown Source) > at org.apache.soap.transport.http.SOAPHTTPConnection.send(Unknown Source) > at org.apache.soap.rpc.Call.invoke(Unknown Source) > at org.apache.soap.rpc.Call.invoke(Unknown Source) > at > de.mc.etnbestterm.data.SoapCallingDataHolder.callSoaply(SoapCallingDataHolde > r.java:75) > at > de.mc.etnbestterm.data.MainDataHolder.connectServerToDB(MainDataHolder.java: > 457) > at de.mc.etnbestterm.data.MainDataHolder.<init>(MainDataHolder.java:61) > at > de.mc.etnbestterm.data.SingletonManager.getMainDataHolder(SingletonManager.j > ava:46) > at de.mc.etnbestterm.gui.WillkommenPanel.jbInit(WillkommenPanel.java:62) > at de.mc.etnbestterm.gui.WillkommenPanel.<init>(WillkommenPanel.java:52) > at de.mc.etnbestterm.gui.MainFrame.<init>(MainFrame.java:40) > at de.mc.etnbestterm.Bestellterminal.jbInit(Bestellterminal.java:64) > at de.mc.etnbestterm.Bestellterminal.<init>(Bestellterminal.java:44) > at de.mc.etnbestterm.Bestellterminal.main(Bestellterminal.java:117) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at com.sun.javaws.Launcher.executeApplication(Unknown Source) > at com.sun.javaws.Launcher.executeMainClass(Unknown Source) > at com.sun.javaws.Launcher.continueLaunch(Unknown Source) > at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source) > at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source) > at com.sun.javaws.Launcher.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > > Otherwise the same application works by different customers which also use a > proxy. > Once when a customer changed the proxy-software the application got timeouts > for every soap-call > Can it be, that some proxies have problems with apache-soap in general? > Does it makes a difference for soap using a certian proxy-software in the > network? > what can be wrong? > > thanks for any hints in advance > > Malte > > PS: One of the customers having trouble is unsing AVM Ken as proxy-server > > > > Scott Nichol Do not reply directly to this e-mail address, as it is filtered to only receive e-mail from specific mailing lists.
