-
Bug
-
Resolution: Fixed
-
P4
-
1.4.0
-
None
-
beta2
-
sparc
-
solaris_8
-
Not verified
On Merlin build 58, tnameserv does not start using the default port:
% su
# cd $JAVA_HOME/bin
# ./tnameserv
caught an exception while starting the bootstrap service on port 900
try using a different port with a commandline arguments -ORBInitialPort <portno>
However, if tnameserv is launched as follows the process initiates correctly.
#./tnameserv -ORBInitialPort 900
Initial Naming Context
IOR:0000....
The correct behaviour is exhibited by the latest Ladybird
build (21).
********************************************************************************
###@###.### 2001-10-24
Fix verified OK:
- using build:j2sdk-1_4_0-beta3-bin-b84-solsparc-20_oct_2001
- by running tnameserv both as normal and super user, with and without the "-ORBInitialPort" option for ports 900 and 1050
********************************************************************************
% su
# cd $JAVA_HOME/bin
# ./tnameserv
caught an exception while starting the bootstrap service on port 900
try using a different port with a commandline arguments -ORBInitialPort <portno>
However, if tnameserv is launched as follows the process initiates correctly.
#./tnameserv -ORBInitialPort 900
Initial Naming Context
IOR:0000....
The correct behaviour is exhibited by the latest Ladybird
build (21).
********************************************************************************
###@###.### 2001-10-24
Fix verified OK:
- using build:j2sdk-1_4_0-beta3-bin-b84-solsparc-20_oct_2001
- by running tnameserv both as normal and super user, with and without the "-ORBInitialPort" option for ports 900 and 1050
********************************************************************************