I hope this is the suitable category to post. We have a cluster of 2 servers on which jrun4 is installed. I am trying to do a simple lookup from a different client machine. I am running the following piece of code for it. Please see the code below:
When I run this java code from the client machine and try to connect to server 1 it gives the following error: C:\>java TesthelloWorldEJB Server is-->10.xxx.xxx.xxx:2908 Looking up for EJB->HelloWorldEJB/HelloWorldEJB javax.naming.CommunicationException [Root exception is java.rmi.ConnectException : Connection refused to host: 192.xxx.xxx.xxx; nested exception is: java.net.ConnectException: Connection timed out: connect] at jrun.naming.JRunNamingContext.lookup(JRunNamingContext.java:502) at jrun.naming.JRunNamingContext.lookup(JRunNamingContext.java:466) at javax.naming.InitialContext.lookup(Unknown Source) Caused by: java.net.ConnectException: Connection timed out: 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 sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown S ource) at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown S ource) at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source) at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source) at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source) at sun.rmi.server.UnicastRef.invoke(Unknown Source) at jrun.naming.ContextManager_Stub.invoke(Unknown Source) at jrunx.cluster.ClusterAlgorithm.invokeService(ClusterAlgorithm.java:83 ) ... 12 more
Even though we are trying to connect to 10.xxx.xxx.xxx, it is connecting to 192.xxx.xxx.xxx. We figured out that the IP Address 192.xxx.xxx.xxx private IP Address of server (The heart beat address used by the cluster).
And, When we try to connect to the server2 on the cluster, from the same client it is succesfull. Please help in solving this issue. Any help to resolve this issue would be appreciated. Thanks in Advance.