RP/MSQ 4.0 (UNIX, NT) - xgroup reconnect link issues with failover entries
(Doc ID 770883.1)
Last updated on JANUARY 28, 2019
Applies to:Oracle MessageQ / MessageQ / 4.0A
Information in this document applies to any platform
MessageQ for UNIX, V5.0-RP22 (main node) MessageQ for UNIX, V4.0A-RP48 (failover nodes) Operating systems: Main server is Solaris 8. Failover servers are Solaris 2.5.1 and HP-UX 10.20 Problem with failover entries in the xgroup table. To reproduce this, I have three machines with the following configurations: 1) lcsol15 - running MessageQ, V5.0-RP22, group 9701 2) lcsol12 - running MessageQ, V4.0A-RP48, group 2007 3) lchp12 - running MessageQ, V4.0A-RP48, group 2007 Only one copy of group 2007 runs at a time. The group.ini and set up files are under: /nfs/home4/wongm/lcsol15/cases/mq/att - for lcsol15 /nfs/home4/wongm/lcsol12/cases/mq/att - for lcsol12 /nfs/home4/wongm/lchp12/cases/mq/att - for lchp12 Thinking that RP50 may have an impact on R47, I tried this with RP50 as well on the failover remote nodes, and was still able to reproduce this using lcsol15 (V5.0A-RP22) as well as V4.0A-RP50 on lcdux2 (/nfs/home4/wongm/lcdux2/cases/mq/att). I had to use lcdux2, since no patches beyond RP48 were available for Solaris and HP-UX. 1)Start lcsol12 start lcsol15 Will connect to lcsol12 Bring down lcsol12, bring up within 2 minutes Will connect to lcsol12 Bring down lcsol12; bring up after several minutes (> 2 minutes) Will not connect to lcsol12 2) Shutdown both remote groups Start lcsol15 After several minutes (> 2 minutes) start lchp12 Will not connect to lcsol15 Note: these links can be started manually through dmqmonc, but is not acceptable to the customer who depends on automatic reconnect. If there is no failover entry for 2007 in the group 9701 xgroup table, link seems to recover automatically.
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