Issue 5853: ORB shutdown should be configurable (java2idl-rtf)
Source: Oracle (Dr. Andrew Piper, andyp(at)bea.com)
Nature: Uncategorized Issue
Severity: 
Summary: Section 1.6.1 states:


"A call to exportObject with no objects exported creates a non-daemon thread that
keeps the Java virtual machine alive until all exported objects have been unexported by
calling unexportObject."


However, there is no implicit way to unexport objects and so this places the burden on the users to do so. It may be that users are not exporting objects themselves but using some layered product that does so - in this case they would have to call a shutdown API in order  for their program to exit. All of these solutions are non-intuitive and not helpful to the user who forgets to call the requied API - their program just does not exit.


I would like to suggest that this behavior be configurable in some way, either via exportObject or via properties so that users and implementors can choose whether or not a particular exported object should cause the VM to stay alive.

Resolution: 
Revised Text: 
Actions taken:
February 7, 2003: received issue
Discussion: 

End of Annotations:=====
X-Sender: andyp@san-francisco.beasys.com 
X-Mailer: QUALCOMM Windows Eudora Version 5.0 
Date: Fri, 07 Feb 2003 16:47:22 -0800 
To: java2idl-rtf@omg.org, issues@omg.org 
From: Andy Piper <andyp@bea.com> 
Subject: ORB shutdown should be configurable 
Cc: rpatrick@bea.com 


Section 1.6.1 states:


"A call to exportObject with no objects exported creates a non-daemon
thread that
keeps the Java virtual machine alive until all exported objects have
been unexported by
calling unexportObject."


However, there is no implicit way to unexport objects and so this
places the burden on the users to do so. It may be that users are not
exporting objects themselves but using some layered product that does
so - in this case they would have to call a shutdown API in order  for
their program to exit. All of these solutions are non-intuitive and
not helpful to the user who forgets to call the requied API - their
program just does not exit.


I would like to suggest that this behavior be configurable in some
way, either via exportObject or via properties so that users and
implementors can choose whether or not a particular exported object
should cause the VM to stay alive.


andy