RP/TUX 6.4 - TMUSREVT does not distribute event message to subscriber.
(Doc ID 768998.1)
Last updated on NOVEMBER 04, 2016
Applies to:Oracle Tuxedo / Tuxedo / 6.4
Information in this document applies to any platform
PRODUCT:TUXEDO with client thread VERSION: 6.4 PLATFORM: SOLARIS 2.7 TMUSREVT server fails to distribute the event message to subscriber with the following configuration setup and operation procedure: SETUP: MP configuration, with four nodes. The event post process is in one of the slave nodes. Two event subscribe processes reside on each of the other two slave nodes. They subscribe to the same event. STEPS TO REPRODUCE: 1. Boot application, send client request to invoke event post. Check that both subscribe applications get the notification. 2. Shutdown one of the slave node (say node1) with subcribe server using "init 6" 3. Cleanup node1 from master machine using tmadmin/bbclean, pclean 4. Reboot tuxedo application in node1 from master node. (will get TPEMATCH error from tpsubscribe() ) 6. Shutdown and reboot again the subscribe process in node1 7. Send client request to invoke the event post. The subscribe process in node1 can never get the notification now. The real problem might be that primary TMUSEVT server never updates its control file when event mib configuration is updated.
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