MQSeries.net :: View topic

oddsock · Posted: Wed May 26, 2004 7:34 pm Post subject:

I am relatively inexperienced in MQ development, and am looking for any kind of best practice or approach to the following problem :

We have a java application that uses MQ to send XML documents to various locations. Our application needs to send to pontentially multiple MQ Queue Managers located most likely in remote locations. The problem I'm dealing with is if, for instance, one of the MQ Queue Managers becomes unavailable. Our applicatioin is such that the order of the XML transactions is significant, and dropping the transactions is also not acceptable. So in this case, currently we have a custom built process of writing the data records to a physical file (in the correct order) and then when the Queue manager comes back, reattach, and resend these data records (which are placed on the queue in a higher priority so that they are pulled off first in the proper order)...So question is, is this a standard practice ? Or is there some MQ mechanism for dealing with this situation ? I've read about using failover Queue managers, but in this case the most likely cause of the failure would be network or machine failure (of the remote machine) and any backup Queue managers would also fall into failure mode as well..

any ideas ?