Re: Trying to track down intermittent classserver problems

> The issue that Dennis brought up is another consideration.  It might be that
> there is a DNS related problem, or a connectivity issue related to which
> interface the traffic is originating on.

Hmm. DNS appeared to be working on both sides (standard ping <server>
worked, for example).

Looking through the ClassServer log files, it appears that the
callback port (to which ClassServer was to respond) was changing with
each request for a downloadable jar. I do recall we checked for a
handful of these ports yesterday, as the exceptions were being logged,
and we did not find them (via netstat) open on the client. However, it
wasn't clear to me how long-lived these ports should be, and in any
case, by the time the exception was produced my guess is the ports
were already closed. A question is whether they were opened, then
closed, never opened at all...? There are no socket-level exceptions
in the client logs; all we have are the CNFEs.

For our client in this case we use default Jini host/port settings
except for the eventListenerExporter (configured via the SDM). The
BasicJeriExporter is configured with a specific IP (bound to a
specific virtual network interface on the client). The port is 0 (e.g.
randomly assigned) for that one endpoint. Other than that, we aren't
specifying particular IP addy or port to listen on.


Patrick

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]