• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (1)

1 shrik commented Permalink

thanks for a very informative article. I have a question please. for #2 approach can 2 different MQ QMs be added to same SiBus as 'Bus member's and have the WAS app work seamlessly ?
meaning - can WAS SIbus be configured so that if 1 QM is down,it can automatically send all traffic to other QM, and load balance messages if both available ? w/o app getting a connection failure (and not have the logic to retry in the app code) at all.
something like how WMB works with its localQM in binding mode which can be part of same MQ cluster as other 2 or more QMs. the MQ cluster work load algorithm would ensure its continuously functioning with no connection failures.

Add a Comment Add a Comment