Name: yyT116575 Date: 04/18/2001


java version "1.3.1-rc1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-rc1-b21)
Java HotSpot(TM) Client VM (build 1.3.1-rc1-b21, mixed mode)

This is closely related to the closed bug ID 4323062. I wish to start some CORBA
servers to run as an NT Service. For reasons not important here, some of
these servers must be run as separate NT processes created with the win32
API call CreateProcess(). Before 4323062 was fixed, these processes would get
shafted whenever anyone logged off NT. But 1.3.1-RC1 fixes that with the -Xrs
option on the command line. Many thanks.

Unfortunately, I also need to start tnameserv from the NT Service and have it
live across logoffs. It doesn't. This renders my CORBA servers, which now
remain, useless since clients cannot find them. Starting another tnameserv after
logoff/login doesn't help because the existing servers are not registered with
the new tnameserv.

-Xrs does work and solve the problem for the JVM. This bug report was about the fact that -Xrs *DOESN'T* work for tnameserv.

I create CORBA servers using -Xrs in the java (or javaw) commands passed to CreateProcess from within the NT Service. The logoff problem has been fixed in 1.3.1-rc1. I.e., the CORBA servers now remain after logoff. But, since it's CORBA, I need a naming service to be running as well. With or without -Xrs, the tnameserv process gets killed during logoff even though the CORBA servers remain. Therefore the CORBA servers are unreachable since the name service does not exist. Starting a new tnameserv later doesn't help since the original CORBA servers do not get re-registered with the new naming service.

The fix seems obvious -- have tnameserv, which is probably a Java app, accept a
-Xrs on the command line and pass it on to the java invocation that runs the
naming service.
(Review ID: 120955)
======================================================================