Issue 1965: Eliminating server wait code (java2idl-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: An RMI-JRMP server creates and exports server objects and then returns. A non-daemon thread created by the JRMP runtime keeps the server process alive until there are no more objects exported. For code portability, an RMI-IIOP server needs to work in a similar way. It is not acceptable to require a call to ORB.run() or the use of application "wait" code to keep the server process alive. I propose that the specification of PortableRemoteObject.exportObject be updated to say that the first call to this creates a non-daemon thread which keeps the JVM alive until all exported objects have been unexported by calls to PortableRemoteObject.unexportObject. Resolution: Revised Text: Actions taken: September 16, 1998: received issue February 23, 1999: closed issue Discussion: End of Annotations:===== Return-Path: Date: Wed, 16 Sep 1998 22:24:05 +0100 From: Simon Nash Organization: IBM To: java2idl-rtf@omg.org CC: issues@omg.org Subject: Eliminating server wait code An RMI-JRMP server creates and exports server objects and then returns. A non-daemon thread created by the JRMP runtime keeps the server process alive until there are no more objects exported. For code portability, an RMI-IIOP server needs to work in a similar way. It is not acceptable to require a call to ORB.run() or the use of application "wait" code to keep the server process alive. I propose that the specification of PortableRemoteObject.exportObject be updated to say that the first call to this creates a non-daemon thread which keeps the JVM alive until all exported objects have been unexported by calls to PortableRemoteObject.unexportObject. Simon -- Simon C Nash, IBM Java Technology Centre, Hursley, UK MailPoint 146, x245156 Tel. 01962 815156 or +44-1962-815156 Internet: nash@hursley.ibm.com Notes mail: Simon Nash@ibmgb