Tuxedo 6.5.3 README

LIBGWT_CAT:1075:ERROR:Unable to create/find local txid from
shared memory
TDM_CAT:3521:ERROR:Unable to process request
LIBGWT_CAT:1063:ERROR:Can not start Autotran transaction
The error condition persisted until the GWTDOMAIN disconnected
from the remote domain and re-connected. Then the GWTDOMAIN
recovered and continued to run.
Solution 10-000210-2604
The System Event server TMSYSEVT incorrectly translated five
system messages to EMS event ZTUX_EVT_SYSTEM_EVENT. The problem
occurred with:
(a) the three TUXEDO system events raised by Jolt,
.SysClientDied
.SysClientState
.SysClientSecurity
(b) event .SysMachineState when raised with CMDTUX messages
4483 and 4485.
TMSYSEVT now makes these correct translations:
.SysClientDied -> ZTUX_EVT_SYS_CLIENTDIED
.SysClientState -> ZTUX_EVT_SYS_CLIENTSTATE
.SysClientSecurity -> ZTUX_EVT_SYS_CLIENTSECURITY
.SysMachineState -> ZTUX_EVT_SYS_MACHSTATE
Solution 10-000224-5593
When statically linking an OSS /WS client, (i.e., the c89 option
-WBstatic was used), three entry points were left unresolved:
tmnw_hosts2n, tmnw_numhost and tmnw_ports2n. This problem could
be worked around by adding -l "-lnws" to the buildclient command.
buildclient now adds the second instance of -lnws when a /WS
client is being statically built.
Solution 10-000602-8423
If a conversational client aborted a conversation (e.g., by
calling tpdiscon()) while the service was in "send" mode for the
conversation, the service did not purge a message transfer file.
The transfer file had to be purged manually, since its intended
recipient, the client, had abandoned the conversation and was
never told that the file existed. These orphaned files occurred
infrequently, since Tuxedo applications usually do not abort
conversations as part of their normal processing.
Message transfer files are created in the application's Guardian
subvolume, and have names of the form "ZZTX####", where "#" is a
hexadecimal digit.
Solution 10-000605-8440
In heavy stress testing, with many clients rapidly doing tpinit()
and tpterm() calls, the WSL could die. The test failed after
approximately 170,000 socket creations/teardowns by the WSL. The
WSL has been improved so that this problem is less likely.
file:///C|/Release 6.5 V3/ReadmeNSTux65v3.txt
file:///C|/Release 6.5 V3/ReadmeNSTux65v3.txt (9 of 13) [4/27/2004 10:38:09 AM]