because of our wrong ip and port configurations only we got the connection time
out exception.
i think the org.jboss.security.ignoreHttpHost = true is disabled the host name
verification. it corrects the java.io.IOException: HTTPS hostname wrong:
exception.
if we get any further issues, then
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
we got the problem and solution.
we mistaken in the protocol name of system properties. actually we specified as
http instead of https. that's the problem. while u r using https, u have to
specify the system properties like https.proxySet.
sample code:
System.setProperty(https.proxySet,
Actually our understanding is whenever we are connecting from jboss remoting
client to jboss remoting server through HTTPS, actually we need to pass the
meta data, otherwise it will throw the exception which is shown in previous
post.(java.io.IOException: HTTPS hostname wrong: should be )
We found that whenever jboss remoting client connect to jboss remoting server
through HTTPS, the hostname is verified.
so we setted the system property like
System.setProperty(org.jboss.security.ignoreHttpsHost, true );
Now we are getting the connection time out exception