Now we got another problem. the above SSL implementation is correctly working with in LAN.
when using proxy server and static ip stuffs, then we are getting this following exception. (java.net.NoRouteToHostException: No route to host: connect) Actually our URI is like https://203.199.209.149:8888 203.199.209.149 is the static ip address. we are setting the proxy settings through the system properties. System.setProperty("http.proxySet", "true" ); System.setProperty("http.proxyHost", "172.24.1.1" ); System.setProperty("http.proxyPort", "80" ); System.setProperty("org.jboss.security.ignoreHttpsHost", "true" ); 172.24.1.1 is the proxy ip address. we are able to ping the proxy ip address. is there any additional configurational settings? what's the exact problem? org.jboss.remoting.CannotConnectException: Can not connect http client invoker. at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:201) at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:80) at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143) at org.jboss.remoting.Client.invoke(Client.java:525) at org.jboss.remoting.Client.addListener(Client.java:720) at org.jboss.remoting.Client.addListener(Client.java:686) at org.jboss.remoting.Client.addListener(Client.java:668) at org.jboss.test.remoting.transport.http.ssl.basic.CallbackNewSSLClient.testPullCallback(CallbackNewSSLClient.java:99) at org.jboss.test.remoting.transport.http.ssl.basic.CallbackNewSSLClient.main(CallbackNewSSLClient.java:141) Caused by: java.net.NoRouteToHostException: No route to host: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:452) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(DashoA6275) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.(DashoA6275) at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(DashoA6275) at sun.net.www.protocol.https.HttpsClient.doConnect(DashoA6275) at sun.net.www.http.HttpClient.openServer(HttpClient.java:402) at sun.net.www.http.HttpClient.openServer(HttpClient.java:618) at sun.net.www.protocol.https.HttpsClient.(DashoA6275) at sun.net.www.protocol.https.HttpsClient.a(DashoA6275) at sun.net.www.protocol.https.HttpsClient.a(DashoA6275) at sun.net.www.protocol.https.HttpsClient.a(DashoA6275) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.plainConnect(DashoA6275) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(DashoA6275) at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:560) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(DashoA6275) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:163) ... 8 more is there any additional configurational settings? what's the exact problem? please reply for this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952569#3952569 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952569 All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
