This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
We are using JBoss 4.0.5.GA as our application server.
The scenario is like this.
Machine A) IP Address: 192.168.XXX.YYY. [It's the Server] On this Machine Jboss4.0.5.GA and MySQL are running.
The outside system (basically the external clients) refers to this machine through address 220.225.ZZZ.XXX. This is the public ip address. i.e the external_host_name = 220.225.ZZZ.XXX.
Machine B) it's an external client. It is looking up for service which is running on Machine A through JNDI. In the client code, the jndi provider URL is set up to "jnp://220.225.ZZZ.XXX:1099" when the initial context is created for the RMI access.
The client code which is running on Machine B) is doing a lookup for the service, using the following jndi.propterties: Code:
The two machines are running on different network.
When am running the code on the Machine B), and trying to access the service running on Machine A), it is throwing java.naming.CommunicationException: connection refused, cannot connect to url: 220.127.116.11.
Can any one guide me as to where we are going wrong and whether we are missing any setting in the JBoss Server?
I need this fix very urgently...please guide be to the solution.