Tuxedo 6.5.3 README

In the following sequence of MIB requests, activation fails for the
server TMQUEUE on a remote machine:
On the local machine:
- add a new local group in the local machine
- activate this local group
- add a new local server TMQUEUE in the local machine
- activate this local server TMQUEUE
On the remote machine:
- add a new remote group in the remote machine
- activate this remote group
- a GET on this group while on the local machine says it's INACTIVE
- a GET of the remote group or the local group while on the remote
machine does not return any group
- add a new remote server TMQUEUE in the remote machine
- activating this remote server TMQUEUE fails intermittently
The remote ulog failures include a strange error saying "invalid
server group name ..." of the local group just added.
5. Solution 10-000914-0294
The following system events indicate that capacity limits have been
reached:
.SysMachineFullMaxconv, message LIBTUX_CAT:1488
.SysMachineFullMaxwsclients, message LIBTUX_CAT:1490
.SysMachineFullMaxaccessers, message LIBTUX_CAT:1491
NonStop TUXEDO detects these events only when BB sanity scans are
done, as a result of tmadmin's bbclean command, or after a BBL has
failed. These events are not raised when a capacity limit is reached
during normal operation.
For example, none of the above system events are raised in the
following situations:
User expected event .SysMachineFullMaxConv, but saw only these errors:
LIBTUX_CAT:328: ERROR: No space in Bulletin Board for Connection Table
LIBTUX_CAT:1079: ERROR: Failed to create connection
User expected event .SysMachineFullMaxwsclients, but saw only these
errors:
LIBTUX_CAT:1122: ERROR: No space in Bulletin Board
LIBTUX_CAT:582: ERROR: Unable to register, registry table full
User expected event .SysMachineFullMaxAccessers, but saw only these
errors:
LIBTUX_CAT:1122: ERROR: No space in Bulletin Board
LIBTUX_CAT:582: ERROR: Unable to register, registry table full
Also, in very rare circumstances involving BBL failure, the system
event .SysClientDied may not be generated when it should be.
6. Solution 10-000915-0302
The script $TUXDIR/bin/tsinfo doesn't work if IPCKEY has less than 4
digits. For example, when IPCKEY is 123, the command:
file:///C|/Release 6.5 V3/ReadmeNSTux65v3.txt
file:///C|/Release 6.5 V3/ReadmeNSTux65v3.txt (12 of 13) [4/27/2004 10:38:09 AM]