Cisco Bug: CSCur02950 - HornetQ redundancy not enabled on Conductor service nodes
Jun 23, 2020
- Cisco Conductor
Known Affected Releases
Symptom: HornetQ instances installed on Conductor service nodes can not be configured in high availability mode. UPM instances on the service nodes must be configured to use a single HornetQ, so if the service node on which that HornetQ operates is brought down, UPM on the other service node will fail. Conditions: Charter DCAS environment, where BOA and UPM are used for household authorizations, and the authorizations have to pass through HornetQ to get to UHE and VGS components.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases