2 Replies Latest reply on Jul 11, 2013 3:27 AM by presenna.vs

Socket connection could not be established

presenna.vs Jun 6, 2013 7:22 AM

My jboss server uses two different IP addresses for clients to connect. One is the Internal IP address that starts with 192.168 and other the external IP address that starts with 135.

I have a web page from which I launch my jnlp application.

When the server is bound to the internal IP address, I am able to access my web application from both the IP addresses. But I am not able to establish a socket connection through 135. (external IP address) from the external environment.

On the client trace I get a connection timedout error.

Could someone let me know how to resolve this.

My Jboss version is 4.2.3

1. Re: Socket connection could not be established

ron_sigal Jun 20, 2013 9:08 PM (in response to presenna.vs)

Hi presenna.vs,

I'm not sure that your issue pertains to Remoting, which is used for EJBs, EJB3s, and JBossMessaging. It isn't used for web communication.

-Ron
1 of 1 people found this helpful
Actions
2. Re: Socket connection could not be established

presenna.vs Jul 11, 2013 3:27 AM (in response to ron_sigal)

Thanks for the reply. The issue was solved by exposing the Naming Service via the external IP address Im able to reach the socket from both the LANs. Previously the InvokerURL was the internal IP address's URL which is the rmi.server.hostname by default.
Actions

Go to original post