-
Bug
-
Resolution: Fixed
-
P3
-
1.4.2
-
b02
-
x86
-
linux, windows_2000
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2120391 | 7 | J. Duke | P3 | Closed | Won't Fix | |
JDK-2158503 | 6u10 | Unassigned | P3 | Closed | Won't Fix | |
JDK-2123093 | 1.4-pool | Ken Cavanaugh | P3 | Closed | Won't Fix |
Name: jl125535 Date: 08/29/2003
FULL PRODUCT VERSION :
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
FULL OPERATING SYSTEM VERSION :
Microsoft Windows 2000 [Version 5.00.2195]
EXTRA RELEVANT SYSTEM CONFIGURATION :
A DESCRIPTION OF THE PROBLEM :
SRC\com\sun\corba\se\internal\corba\InitialNamingClient.java
contains the following code:
>>>>>
// 2089 is the default port number according to INS spec.
// GIOP 1.2 is the default version.
int port = 2089;
int major = 1;
int minor = 2;
<<<<<
But page 88 of the document at http://omg.org/cgi-bin/doc?ptc/00-08-07 (listed as a specification reference on http://java.sun.com/j2se/1.4.2/docs/api/org/omg/CORBA/doc-files/compliance.html) indicates that the correct values are port 2809 and version number 1.0.
EXPECTED VERSUS ACTUAL BEHAVIOR :
When using a corbaloc specification for an ORB supporting
only up to version 1.1, say, a org.omg.CORBA.COMM_FAILURE
occurs as a result of a MessageError originating at the
remote ORB. When explicitly adding 1.0@ (the version) to the
corbaloc specification, the communication can go ahead. I
have not tested the thing about the default port.
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER WORKAROUND :
Explicitly add version, port.
(Incident Review ID: 164228)
======================================================================
FULL PRODUCT VERSION :
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
FULL OPERATING SYSTEM VERSION :
Microsoft Windows 2000 [Version 5.00.2195]
EXTRA RELEVANT SYSTEM CONFIGURATION :
A DESCRIPTION OF THE PROBLEM :
SRC\com\sun\corba\se\internal\corba\InitialNamingClient.java
contains the following code:
>>>>>
// 2089 is the default port number according to INS spec.
// GIOP 1.2 is the default version.
int port = 2089;
int major = 1;
int minor = 2;
<<<<<
But page 88 of the document at http://omg.org/cgi-bin/doc?ptc/00-08-07 (listed as a specification reference on http://java.sun.com/j2se/1.4.2/docs/api/org/omg/CORBA/doc-files/compliance.html) indicates that the correct values are port 2809 and version number 1.0.
EXPECTED VERSUS ACTUAL BEHAVIOR :
When using a corbaloc specification for an ORB supporting
only up to version 1.1, say, a org.omg.CORBA.COMM_FAILURE
occurs as a result of a MessageError originating at the
remote ORB. When explicitly adding 1.0@ (the version) to the
corbaloc specification, the communication can go ahead. I
have not tested the thing about the default port.
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER WORKAROUND :
Explicitly add version, port.
(Incident Review ID: 164228)
======================================================================
- backported by
-
JDK-2120391 corbaloc default version/port must be 1.0/2809, not 1.2/2089
- Closed
-
JDK-2123093 corbaloc default version/port must be 1.0/2809, not 1.2/2089
- Closed
-
JDK-2158503 corbaloc default version/port must be 1.0/2809, not 1.2/2089
- Closed