Tuxedo 8.0 README for H06.03

Core_README.txt
immediately, before the transaction commits, and remains on its queue
if the transaction aborts. A nonpersistent message that is dequeued
in a transaction is not reinstated on its queue if the transaction is
aborted. This limitation is not present in BEA Tuxedo /Q.
8. Solution 10-021008-2301
If a TMQFORWARD server is dequeuing nonpersistent messages from a
queue space that is also open by a TMQUEUE server, and if the TMQUEUE
server fails, the TMQFORWARD server will write one or more error
messages to the application log file about an invalid transaction id
(error 78) encountered while reading the queue space. The messages
should cease when a new TMQUEUE server starts running and opens the
queue space.
9. Solution 10-021008-2302
If a Tuxedo native client invokes a service using tpcall(), or a
tpacall() eventually followed by a blocking tpgetrply(), and if the
service function sends an unsolicited message to the client using
tpnotify() with the TPACK flag, the service and the client may both
become blocked until either the tpnotify() or the tpgetrply() times
out. This is because the client cannot receive the unsolicited
message while it is blocked in tpgetrply(), and the tpnotify() cannot
complete until the client receives the message.
This behavior is the same in BEA Tuxedo and NonStop Tuxedo. It can be
avoided by not using the TPACK flag with tpnotify(), or by configuring
the client as a workstation client, or by invoking the service using
tpacall() with the TPNOREPLY flag.
10. Solution 10-021008-2307
In the Administrator for NonStop Tuxedo (web GUI), the Statistics Tool
window has the following problems:
(a) The Select button displayed as Cancel. The Select dialog box has
"OK" as its title instead of "Select Objects", and the buttons in it
are "Apply" and "Displaying", instead of the expected "OK", "Apply"
and "Cancel".
(b) If you click the "Resume" button, the word "STATISTICS" appears in
the button.
11. Solution 10-021008-2312
TMQUEUE may issue TDM_CAT:1005 errors due to a race condition. The
result is an inconsistent Queue Space, which must be destroyed and
recreated. This problem can happen when the expiration time of a
message is within an application's SANITYSCAN interval of its birth
time. A message can acquire such a birth time if it is aborted and
its queue has a retry delay. The problem can be avoided by setting
the queue's retry delay to zero.
12. Solution 10-021008-2316
On rare occasions, the TMQUEUE server wrote this message to the
application log file:
TDM_CAT:1005: ERROR: READUPDATELOCK(< queue-space>) failed
with file error 21
Here <queue-space> is the physical name of the queue space opened by
Page 8