We are using version 5.0.4 of WBIMB, accessing a clustered
5.3 queue manager. We have flows
that put messages onto a clustered queue that is hosted by several other servers. However, since the workload exit is
driven at MQOPEN time, and since the broker doesn't issue a MQCLOSE after
doing a put, we really aren't getting the benefits of the workload exit to
round robin these messages to all of the other servers, but instead are really
basically fixed to one server.
Obviously if components are stopped and started you might drive to a
different server, but in general, once the broker has attached himself to a
clustered queue instance, it stays with that instance.
My question is, how are
other folks handling the load balancing issues when coming out of the broker? Do you just live with the fact that you're
linked to one, or have you implemented any solutions?
We've raised a requirement on this, but
wondered if there were any solutions out there.
Thanks.
Tim
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.comArchive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
