How To Change A Tuxedo Cross Domain Event Attribute So It Will Not Be Persisted?
(Doc ID 1980624.1)
Last updated on DECEMBER 10, 2019
Applies to:
Oracle Tuxedo - Version 12.1.1 and laterInformation in this document applies to any platform.
Goal
The Tuxedo cross domain event is publishing as persistent, so if a Tuxedo GWTDOMAIN process, or the machine, crashed the event is no longer unsubscribed.
After a crash, the following message is output at the next boot of a Tuxedo GWTDOMAIN server process.
221836.server!GWTDOMAIN.xxxx.1594410752.0: LIBGW_CAT:5392: ERROR: tpsubscribe event "TESTEVENT1" with expr "TESTEVENT1" with filter "" failed
A Tuxedo administrator needs to remove the tmusrevt.dat file in order to clear the event.
To avoid this, how to change the event attribute for cross domain so it is not persisted?
Here is an example tmusrevt.dat, the event subscribed with TA_EVENT_PERSIST
TA_EVENT_PERSIST 1
TA_EVENT_GWEVT 1
TA_SUBSCRIPTION_VERSION 2
TA_SUBSCRIPTION_HANDLE 1000000000
TA_EB_PID <pid#>
TA_EB_MID 0
TA_CLASS T_EVENT_SERVICE
TA_SERVICENAME ..GWEVTTESTEVENT1TDOM1TDOM2
TA_EVENT_EXPR TESTEVENT1
TA_EVENT_GWEVT 1
TA_SUBSCRIPTION_VERSION 2
TA_SUBSCRIPTION_HANDLE 1000000000
TA_EB_PID <pid#>
TA_EB_MID 0
TA_CLASS T_EVENT_SERVICE
TA_SERVICENAME ..GWEVTTESTEVENT1TDOM1TDOM2
TA_EVENT_EXPR TESTEVENT1
Solution
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
| Goal |
| Solution |
| References |