-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P2
-
Affects Version/s: 1.4.0
-
Component/s: other-libs
-
None
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2041218 | 1.4.0 | Hemanth Puttaswamy | P2 | Closed | Won't Fix |
First occured in: Merlin build b32
tnameserv does not warn about ports already in use, and simply starts up the service on the same port.
Have attached two logs that show the differing behavior. Build b31 warns about an existing process listening in on that port, but build 32 does not.
******************************************************************************
###@###.### 2001-08-13
build - j2sdk-1_4_0-beta_refresh-bin-b75-solsparc-09_aug_2001
Result - tnameserv gave a warning when tried to start 2 services on the same port.
*******************************************************************************
tnameserv does not warn about ports already in use, and simply starts up the service on the same port.
Have attached two logs that show the differing behavior. Build b31 warns about an existing process listening in on that port, but build 32 does not.
******************************************************************************
###@###.### 2001-08-13
build - j2sdk-1_4_0-beta_refresh-bin-b75-solsparc-09_aug_2001
Result - tnameserv gave a warning when tried to start 2 services on the same port.
*******************************************************************************
- backported by
-
JDK-2041218 tnameserv does not complain about ports already being used.
-
- Closed
-