CORBA 2.3 Update 3 README

+ the change was in a header, which is forbidden in a C++ IPM
+ this method was used internally by the ORB, but the callers
were not re-coded to delete the memory.
The latter problem caused memory to be leaked with every method
invocation.
This problem has been fixed by reverting the header to its
original (non-compliant) form.
(SOLN 10-011001-3482)
Known Problems Remaining:
1) For C++ applications, although a type of long long is allowed as
a union discriminant, the union case values are restricted to the
range of an enum (32 bit integer). This is due to NonStop
DOM's union implementation. This restriction may be lifted in
the future.
(SOLN 10-010808-2044)
2) For NonStop CORBA 2.3, CPU Up system messages are incorrectly
logged as Severity Error. CPU Up messages are actually benign
when received by NonStop CORBA 2.3. NonStop CORBA 2.3
servers configured with fs_server or tsmp_server set true will
generate an event similar to the following:
Error No: 1100; RcvEH::handle_event, unknown msg:-3,
Severity: Error,
Component: Application, PName: \NSDQA1.$Z1ZM,
Pid: 45219850, Tid: 2,
File: gfsehoss.cpp, Line: 1326
The server will continue to operate normally.
(SOLN 10-010808-2045)
3) Using the ostream insertion operator (<<) causes a process
to fail due to unresolved references.
(SOLN 10-010909-2935)
4) For NonStop CORBA 2.3, the Java ORB does not correctly
demarshal value types whose tag is "no type information".
(SOLN 10-010912-3014)
5) NonStop CORBA 2.3 does not handle demarshalling NonStop
CORBA 2.3 object references when a) exporting and importing
processes share NonStop Himalaya S-series system and
ORBprofile argument, and b) servant uses a stateless POA.
(SOLN 10-010912-3015)
6) Some CORBA processes will abend if they lose the startup
race with the Name Service because the Name Service is not
ready to accept requests.
(SOLN 10-010913-3059)
file:///C|/Corba Readmes/ReadmeCORBA23u3.txt
file:///C|/Corba Readmes/ReadmeCORBA23u3.txt (9 of 15) [4/27/2004 11:41:35 AM]