Tuxedo Workstation Clients Hang On OpenVMS
(Doc ID 1452147.1)
Last updated on SEPTEMBER 18, 2023
Applies to:
Oracle Tuxedo - Version 11.1.1.2.0 and laterInformation in this document applies to any platform.
Symptoms
There are three symptoms for how this problem presents itself:
1)On OpenVMS Tuxedo clients are created by a control/parent process. If the control process is then killed with stop/id some workstation clients will hang.
After the hang new workstation clients are unable to connect to Tuxedo as the workstation handler appears to be deadlocked by the hang.. A hard kill recovery is required to continue.
2)A similar symptom also occurs without using stop/id by just setting the Tuxedo TMTRACE logical before booting the application.
3) Finally, without using stop/id or TMTRACE, TBEBLOCK/TPESYSTEM/TPELIMIT errors are received by the client applications using tpacall() under heavy load with the following messages:
175551.mymachine!?proc.826510770.2068770496.0: LIBWSC_CAT:1029: ERROR: Unable to retrieve stored reply
Changes
Upgraded from Tuxedo 6.5 for OpenVMS 7.3 on Alpha to Tuxedo 11.1.1.2.0 for OpenVMS 8.4 on Itanium
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |