Glad to hear you found the problem. I do not know of a standard way to determine whether there is a proxy, but I am certainly not an expert on the subject.
On 5 Jun 2003 at 9:58, Malte Kempff wrote: > Hi Scott, > > I saw now cause of the problem. Thanks for your hint it helped me. The > property in the file was set manually > and its name was written in the wrong way. > I have now one check more to recognice a missing proxy looking for the other > String "java.net.NoRouteToHostException". > By the way, is there a better technique to determine a proxy than to look > over the exception Message? > > -----Ursprungliche Nachricht----- > Von: Malte Kempff [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 5. Juni 2003 09:26 > An: [EMAIL PROTECTED] > Betreff: AW: Problem with Host-connection in combination with some > Proxies > > > Hi Scott, > > The proxy's Address is asked to the user via a dialog and the Information > are then stored as properties in a file. > the proxy-information is set to soap with something like this > > > st.setProxyHost(proxyHost); > st.setProxyPort(Integer.parseInt(proxyPort)); > > SOAPContext ctx = new SOAPContext(); > ctx.setGzip(true); > Call call = new Call("urn:Bestterm", > callName, > params, > null, > Constants.NS_URI_SOAP_ENC, > ctx > ); > call.setSOAPTransport(st); > ... > > > > The Dialog pops up when there is a Soap-Exception with the Message > something like this > > catch (SOAPException sEx) > { > if ( sEx.getMessage().indexOf("Error opening > socket:")>-1 > ||sEx.getMessage().indexOf("Connection > refused:")>-1) > > .... popup Dialog an get proxy infos > > }//end of catch (SOAPException sEx) > > > In the traces I see that the Proxy-properties are set, so I suppose that > they are set. > > for detail I send the class, which manages all the soap calls, as > attachment. > > thanks in advance > > Malte > > > -----Ursprungliche Nachricht----- > Von: Scott Nichol [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 4. Juni 2003 21:23 > An: [EMAIL PROTECTED] > Betreff: Re: Problem with Host-connection in combination with some > Proxies > > > "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. > > > > > Scott Nichol Do not reply directly to this e-mail address, as it is filtered to only receive e-mail from specific mailing lists.
