I'm somewhat baffled by your opening statement here. There's nothing in an
RMI server that automatically gives it repeating behavior and in any case
where would it send the message as you havn't mentioned clients. At first I
figured that you're talking about RMI callbacks.  However, you might mean
that the server process prints text every 5 seconds.  In either case, it
seems the culprit is the thread you make to do this 5-second printing.  That
process will not be affected by you unbinding the server.  The server
binding affects its ability to accept requests, but doesn't affect
connections already in place.  The callback object is essentially a
different server with a different connection--it will keep going until you
stop your thread.  If it's just the text, you must stop that thread
yourself.

It sounds like your registration thread is really a loop, which explains the
repeating behavior.

A normal RMI server responds to requests, any of which might individually
fail, but that normally doesn't affect the operation of the listening
process.  The server is considered crashed when it stops accepting
connections.  If your server has an internal process--its operation is
separate from how it accepts requests.

Can you describe in more detail what your server really does or post a
simplified (very simplified) version of your server that exhibits this
behavior?

Matt Humphrey matth@ivizNOSPAM.com http://www.iviz.com/