RP/TUX 8.1/TUX 9.1 - BB Corruption When Sending New BB In MP Mode (Doc ID 777576.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo - Version 8.1 to 9.1
Information in this document applies to any platform.
Information in this document applies to any platform


Tuxedo 8.1 MP Mode

When sending new tuxconfig in MP mode, if the client calls tpterm(), BB corruption is as follows. After this case, need to reboot non-master node.


234328.masterBoxname!DBBL.15882.1.0: CMDTUX_CAT:1392: ERROR: BBL broadcast reply timeout, machine= FILESRV2 opcode= 0x1d000022
234328.masterBoxname!DBBL.15882.1.0: CMDTUX_CAT:1394: ERROR: BBL partitioned, machine= FILESRV2
234328.masterBoxname!DBBL.15882.1.0: CMDTUX_CAT:1385: INFO: BBL now unpartitioned, machine= FILESRV2
234328.masterBoxname!DBBL.15882.1.0: CMDTUX_CAT:1762: INFO: Sending new TUXCONFIG file to machine FILESRV2
234328.masterBoxname!DBBL.15882.1.0: CMDTUX_CAT:672: INFO: Sending BBL on machine FILESRV2 new version of bulletin board
234333.masterBoxname!DBBL.15882.1.0: CMDTUX_CAT:668: WARN: Stale message received from BBL on machine FILESRV2

Non master-node

234310.slaveBoxname!tlisten.12860.1.-2: CMDTUX_CAT:4209: INFO: Accepted request from //, seq # 459
234316.slaveBoxname!simpserv.941.1.0: LIBTUX_CAT:522: INFO: Default tpsvrdone() function used
234316.slaveBoxname!simpserv.941.1.0: LIBTUX_CAT:329: ERROR: Tried to free non-alloced tmrte
234328.slaveBoxname!BBL.904.1.0: WARN: Wanter(s) of USEM[0] stuck - waking


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms