I am having trouble testing EJB across network.

Question

I am trying to test an ejb client, with jboss being the App Server, that would call a method of an EJB running on say "theserver.domain.com" machine. I get the following error when I run the client program from my PC.
The EJB and client works fine when jboss and client is on the same machine.
This is an example that comes from jboss site (http://www.jboss.org/doco_files/) called documentation-example.zip. I have modified the client as listed below. However, I have not touched the InterestBean which contains one business method called calculateCompoundInterest. It's very straight forward.
Does any one see anything wrong with the client code. Do you have to do anything special when deploying EJB to "theserver.domain.com" vs. running locally with client.
Thanks for your help.
Error:
[java] Got context
[java] javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
[java] java.net.ConnectException: Connection refused: connect]
Code:
package org.jboss.docs.interest;
import java.rmi.RemoteException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
import java.sql.*;
import javax.sql.DataSource ;
import oracle.jdbc.driver.* ;
import oracle.jdbc.* ;
import javax.naming.InitialContext ;
import javax.naming.NamingException;
import javax.naming.Context ;
This class contains the implementation for the `calculateCompoundInterest'
method exposed by this Bean. It includes empty method bodies for the methods
prescribe by the SessionBean interface; these don't need to do anything in this
simple example.
class InterestClient
/** This method does all the work. It creates an instance of the Interest EJB on
the EJB server, and calls its `calculateCompoundInterest()' method, then prints
the result of the calculation.
public static void main(String[] args)
// Enclosing the whole process in a single `try' block is not an ideal way
// to do exception handling, but I don't want to clutter the program up
// with catch blocks
try
Properties env = new Properties();
env.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
env.setProperty("java.naming.provider.url", "jnp://theserver.domain.com:1099");
env.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
// cachedCTX = new InitialContext(env);
// Get a naming context
InitialContext jndiContext = new InitialContext(env);
// InitialContext jndiContext = new InitialContext();
System.out.println("Got context");
// Get a reference to the Interest Bean
Object ref = jndiContext.lookup("interest/Interest");
System.out.println("Got reference");
// Get a reference from this to the Bean's Home interface
InterestHome home = (InterestHome)
PortableRemoteObject.narrow(ref, InterestHome.class);
// Create an Interest object from the Home interface
Interest interest = home.create();
// call the calculateCompoundInterest() method to do the calculation
System.out.println("Interest on 1000 units, at 10% per period, compounded over 2 periods is:");
System.out.println(interest.calculateCompoundInterest(1000, 0.10, 2));
catch(Exception e)
System.out.println(e.toString());

Answer 1

Hello! We have the same firewall problem with JBoss 2.4.x as App. Server and a Java Application (Swing) as EJB client. How did you go around it?