Java RMI unbind problem.

[Gama Franco]

Hi,

I'm using RMI in my application, but I faced a little problem. When my
program finishes I unbind the RMI object from the registry but the
program doesn't exit after that. I need to press ^C to quit the program.

What did I miss?

Best regards,
Gama Franco

 

[Gerbrand van Dieijen]

Hi,

I'm using RMI in my application, but I faced a little problem. When my
program finishes I unbind the RMI object from the registry but the
program doesn't exit after that. I need to press ^C to quit the program.

Doesn't system.exit(..) work?

 

[Gama Franco]

Doesn't system.exit(..) work?

It worked, thanks.

Is there any reason for the System to hang when the method main is
supposed to return?

Gama Franco

 

[Roedy Green]

Is there any reason for the System to hang when the method main is
supposed to return?

Most of the interesting stuff happens in a GUI app ONLY after main has
exited. The AwT or Swing thread in still alive fielding keypresses and
mouse clicks.

You need to close all the gui stuff down or call System.exit.

 

[Roedy Green]

Most of the interesting stuff happens in a GUI app ONLY after main has
exited. The AwT or Swing thread in still alive fielding keypresses and
mouse clicks.

For details see http://mindprod.com/jgloss/main.html
and http://mindprod.com/jgloss/jframe.html

 

[Gama Franco]

Most of the interesting stuff happens in a GUI app ONLY after main has
exited. The AwT or Swing thread in still alive fielding keypresses and
mouse clicks.

You need to close all the gui stuff down or call System.exit.

I'm using the console, and I'm just curious to know why this happens.

 

[Roedy Green]

I'm using the console, and I'm just curious to know why this happens.

The rule is the program keeps going until the last thread dies. It in
100% console app, the thread running main has nothing else to do after
running main so it dies.

Either than thread or some other thread is still alive fielding gui
events. That thread only dies when the last frame closes, and
sometimes not even then (I think this may be a bug in Swing). So I
kill explicitly when the last frame shuts down.

As I said before, the easiest way it to capture the close of the
master frame and exit . See http://mindprod.com/jgloss/jframe.html
for details.

 

[Esmond Pitt]

I'm using the console, and I'm just curious to know why this happens.

It happens because you haven't unexported the remote object.