-
Bug
-
Resolution: Fixed
-
P3
-
1.4.0
-
None
-
merlin
-
sparc
-
solaris_2.5
-
Verified
The command line prompt "tnameserv" that starts the
CORBA Naming Service accepts a parameter "-ORBInitialPort" for
specifying the port that the server listens on. It appears to accept a
value of "0" which indicates that the server starts up on a random
available port (ref java.net.ServerSocket). However, the diagnostic
printout that results in a terminal window states that the server was
starte on port 0. It would be nice if printout reflected the actual
port number used, otherwise there is no way of determining it
CORBA Naming Service accepts a parameter "-ORBInitialPort" for
specifying the port that the server listens on. It appears to accept a
value of "0" which indicates that the server starts up on a random
available port (ref java.net.ServerSocket). However, the diagnostic
printout that results in a terminal window states that the server was
starte on port 0. It would be nice if printout reflected the actual
port number used, otherwise there is no way of determining it