Nelson Minar wrote:
> >> I ran the same piece of code on jdk1.1.6 in linux, and on jdk1.2 in
> >> NT. But the behaviour is quite different. In both cases the server
> >> and the client waits. Is it a porting problem or a feature?
> >Well, you've got me beat now! I've never seen rebind() wait on any OS
> >or any JDK !!
>
> I have. Personally, I've never had to worry about making sure my RMI
> programs don't exit, although at this point I have so many threads
> running that I don't really know what's going on :-)
>
> I've found that RMI is a bit vague about whether it will ever allow
> the VM to exit. It creates a lot of threads of its own, and they may
> not all be properly marked daemon.
Yup, you're right, Nelson. I've just had another look at my standard chunk of
rmi server code, which waits for and processes System.in input. Guess I've never
tried this without that bit of code !!
A little knowledge is a dangerous thing!
However, the program does exit via System.exit() when I ask it to.
Nick
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
