CORBA 2.3 Update 3 README

5) [B12] Previously, tracing and logging to < STDOUT> could result
in indefinite delays between generation of data and availability
of the data when STDOUT is piped to a file.
T8432 (native C RTL) AAN and before set STDOUT to use line
buffering (as opposed to full buffering); AAO and later versions
set line buffering only if STDOUT is an interactive device. Full
buffering is more efficient with large amounts of data. Line
buffering forces data to be flushed immediately, making things
like "tail -f app.log" and sharing trace files more intuitive.
Logging has been corrected to always set line buffering when
configured to use < STDOUT>.
Tracing has been corrected to make full buffering for STDOUT
optional. The default action will be to set line buffering when
configured to use < STDOUT>. To disable line buffering:
oss> export NSDOM_CFG_TRACE_FULL_BUFFERING=1
(SOLN 10-010711-1534)
6) [B12] During the tracing of GFSIOP file system protocol event
framework receive messages, the device name used during an open
was not recorded. The trace message did not record the name of
the device. Trace message problems such as "FENOSUCHDEV"
reported the problem but not the name of the device that could
not be found.
(SOLN 10-010731-1891)
7) [B12] The default OSS directory for pax files in the workstation
SDK/RTK installer was incorrect.
(SOLN 10-010813-2153)
8) [B12] The installer uses the default OSS directory (Guardian
subvol) of the install as the default location for EMS template
object files (e.g. ZDOMTMPL). Instead it should have a default
thus allowing the person installing to select a location
different from the default. The default location is now
$(USER).ZTEMPL.
(SOLN 10-010813-2155)
9) [B12] In the following scenario:
A client process begins a transaction. The client process
then invokes an operation on a server process's transactional
servant object. The servant object then invokes a callback
operation back to a transactional object within the original
client process.
Then after the callback returns to the client process, the client
will no longer have the original TMF transaction as its process
current transaction. Subsequently, any SQL operation will fail
with FEINVTRANSID (78). This has been corrected.
(SOLN 10-010814-2194)
10) [B12] Previously, the comm server and direct-tcp-server processes
file:///C|/Corba Readmes/ReadmeCORBA23u3.txt
file:///C|/Corba Readmes/ReadmeCORBA23u3.txt (7 of 15) [4/27/2004 11:41:35 AM]