Re: RMI cleanup

I tried, but failed to reproduce the problem in a controlled development
environment.  Essentially, I ran the same RMI server with a
-Djava.rmi.server.hostname=bogus argument, and several clients connecting to
it,  each getting the host not found exception.  Eventually, after
shortening the sleep to 100ms and with six clients running at the same time
on a machine that's only a fraction of the size of the one on which the
problem occurred, I gave up because the increase in load was not
significant.

It seems I may be barking up the wrong tree, or at least there may be a
combination of things that caused the problem.  Heaven knows what.  I hope
it's gone for good.  Thanks guys for your input anyway.
-- 
View this message in context: http://www.nabble.com/RMI-cleanup-tp23310928p23332031.html
Sent from the Java - RMI mailing list archive at Nabble.com.

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff RMI-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

For a list of frequently asked RMI questions please refer to:
http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html

To view past RMI-USERS postings, please see:
http://archives.java.sun.com/archives/rmi-users.html