RMI on Debian: Connection Timed Out: connect

Question

Hi
I have a Problem with my RMI Server program running under Debian.
When i start the server it lasts for about 3 minute until the Object is bound to the RMI-Registry.
I have a simple System.out.println("XXX bound"); statement after binding the registry.rebind(name, stub);
Well it seems to work because no exception is thrown and i can see the println.
But the big problem is, that it takes for about 3 minutes until this is done. when i try to connect to the server via the client,
i get a
"Connection refused to host: xxxxx; nested exception is:
java.netConnectException: Connection timed out: connect"
after a minute, the serverside doesn't make anything, no System.out statement is executed in the remote method.
it seems that RMI is very slow on my Server machine and i can't figure out why.
here are the properties set in the server program:
System.setProperty("java.rmi.server.codebase", "xxxxxx"); //works
     System.setProperty("java.rmi.server.hostname", "xxxx.ath.cx"); //perhaps the problem
     System.setProperty("java.security.policy", "/var/www/dod/xxxxx.policy"); // should be no problemmy client is startet via webstart from the same server an has the lookup code:
try {
               registry = LocateRegistry.getRegistry("xxxx.ath.cx"); //perhaps the problem
               idodsrmi = (XXXServerRMI) registry.lookup("xxxxxxx");
               usrh = idodsrmi.getUserHandle(args[0], args[1]);
          } catch (AccessException e) {
               JOptionPane.showMessageDialog(null, e.getMessage());
               e.printStackTrace();
          } catch (RemoteException e) {
               JOptionPane.showMessageDialog(null, e.getMessage());
               e.printStackTrace();
          } catch (NotBoundException e) {
               JOptionPane.showMessageDialog(null, e.getMessage());
               e.printStackTrace();
          } this code is executed without throwing an exception, but when i try to call methods on usrh i get the connection timeout...
i can't see where the problem is, "xxxx.ath.cx" is the domain name my network is available from outside the lan,
my router forwards port 80 and 1099 to my serverbox
any ideas about the timeout?

Answer 1

Yes that was it, i got the clou when i changed the hostname of my debian-box to xxx.ath.cx. after changing to that hostname i got an exception to google for.. ;-) But it's still strange to get no exception when the hostname of my debian-box differs from the dyndns name. it just lasts for about 3 minutes and seems to work...
Well now im back to an older problem, my server uses hibernate to communicate with a db and when i make 2 .jars (1 hibernate-util with all hibernate related jars and 1 for my project) instead of 1 big jar with all jars i get the exception "No Persistence provider for EntityManager named DOD", thats a strange behavior too because the persistence.xml is at the same place in my project .jar... :-/