We have plans to implement a MQ Solution that makes best use of clustering instead of distributed queueing across multiple tiers. Our main aim is provide a highly available solution for middleware integration. My problem now is concerned with recovery procedures from hardware failure. If one of my nodes in the cluster complete dies through hardware failure, I want to be able to recovery the messages that might be marooned on the SYSTEM.CLUSTER.TRANSMIT.QUEUE. I can probably recovery the Queue Manager itself in some way or another, but it will not be able to communicate with the cluster again without completely destroying and recreating that queue manager. I want to know how I can retrieve messages from the SYSTEM.CLUSTER.TRANSMIT.QUEUE. What have you done in you systems to underwrite the possibilities of this happening? Is there a method of stripping the TRANSMISSION HEADER and MQMD from a message on this queue? I could easily make a small application if the API facilities are available. All comments will be appreciated.
Leon
Relive the FIFA World Cup goals with exclusive video highlights!
http://fifaworldcup.yahoo.com/fc/en
