Re: RMI and java.rmi.server.hostname

2006-01-13 Thread Lorenz Witte
Tom Tromey wrote: Your patch looks like it would help, but it doesn't address all the issues. It seems reasonable to use it as an interim solution though. It sounds like by default we're using 127.0.0.1 -- does this happen with the JDK as well? Sun's JDK? Works nicely with

Re: RMI and java.rmi.server.hostname

2006-01-12 Thread Mark Wielaard
Hi, On Wed, 2006-01-11 at 13:54 -0700, Tom Tromey wrote: I filed a PR: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25754 I would have linked to your message but, weirdly, it isn't in the list archives yet. The official archives are only updated every 12 hours (*). It is available as:

RMI and java.rmi.server.hostname

2006-01-11 Thread Lorenz Witte
Hello everyone, I've been experimenting a little with RMI and GNU Classpath and ran into troubles when client and server were running on different machines. In my setup the client hercules is trying to access a UnicastRemoteObject on the server galahad. The client is able to receive the

Re: RMI and java.rmi.server.hostname

2006-01-11 Thread Tom Tromey
Lorenz == Lorenz Witte [EMAIL PROTECTED] writes: Lorenz Currently I meet the problem by modifying the static constructor of Lorenz gnu.java.rmi.server.UnicastConnectionManager, so that the static field Lorenz localhost is initialized with the value of the Lorenz java.rmi.server.hostname property