Tuxedo 8.0 Update 1 README
In the Administrator for NonStop Tuxedo (web GUI), the Work Station
Listener (WSL) class object shows no data in the Configuration Pane
for an active WSL. We need to click on the Refresh button to get
the values on the Pane.
X. Known Problems List
1. Solution 10-021003-2175, Solution 10-021008-2313
In a stress test with 5 non-GUI Jolt clients on a Solaris machine,
each client starting 20 threads at the same time, intermittent
problems prevented connection to the Jolt Handler (JSH) a few times.
The errors reported by the client's JVM were:
new JoltSession failed
Cannot connect to xx.xxx.xxx.xxx
Reason:NwHdlr: open: Bad Challenge Response
or
new JoltSession failed
Cannot connect to xx.xxx.xxx.xxx
Reason:NwHdlr: Network Error: J_CHALLENGE FAILED
On the HP NonStop server, the NonStop Tuxedo ULOG file contained
warnings in this form:
<time>.<machine>.<cpu>!JSH.<pid>.0.-2: JOLT_CAT:1198:
"WARN: Forced shutdown of client; user name ''; client name ''"
These errors are rare and intermittent under high connection rates.
The client may continue running, or may hang. The problem occurs at
approximately the same rate in NonStop Tuxedo Release 6.5V3 and 8.0.
If the client is hung, it has to be restarted. If the client is not
hung, it should retry the connection.
2. Solution 10-021003-2177, Solution 10-021003-2178
When ENCRYPTBITS in $TUXDIR/udataobj/webgui/webgui.ini has a non-zero
value, for example, ENCRYPTBITS=40, then the Administrator for NonStop
Tuxedo (web GUI) client browser cannot log on to the server for the
Administrator. The client sees an error window with the message,
"Connection Failed!".
3. Solution 10-021007-2255
A queue space that is currently opened by a TMQUEUE or TMQFORWARD
server cannot be accessed by a qmadmin session, nor by a /Q MIB
request. Similarly, a queue space that is currently opened by a
qmadmin session cannot be accessed by a TMQUEUE or TMQFORWARD server.
This limitation is not present in BEA Tuxedo /Q.
4. Solution 10-021007-2259
The tpgetrply() ATMI function does not work correctly with the
TPGETANY option flag in multi-contexted clients. tpgetrply(TPGETANY)
may discard reply messages intended for other contexts in the client
process. Then, when one of the other contexts calls tpgetrply(), it
will return TPETIME because the reply message is no longer available.
5. Solution 10-021008-2277
file:///C|/Release 8.0 Update 1/ReadmeNSTux80u1.txt
file:///C|/Release 8.0 Update 1/ReadmeNSTux80u1.txt (9 of 12) [4/27/2004 10:46:32 AM]