This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Closing as no further followup to previous comment and questions.
The MQ Appliance high availability feature supports a network latency of up to 10ms for the replication link. As the network latency increases the synchronous replication of data takes longer and the performance of disk I/O degrades. The MQ Appliance does not support latencies above 10ms for synchronous replication because the performance impact is then too great for the majority of deployment patterns. The appliances can still communicate and exchange heartbeats at higher latencies, so more information is needed to understand why your queue managers were stopped. Can you please clarify your configuration, the network problem you encountered, the behaviour you observed, the behaviour you would like, and the maximum latency that you would like to be supported. Thank you.
In our installation we have network equipment as intermediaries between the appliance pair comunications.
If a network device has an error, the latency between both mqappliance increases, causing them to stop in an orderly until deciding which appliance should have the MQ managers running.
What we ask is that the threshold of said latency be configurable or that it can be extended to avoid these problems.
It's not clear from the description what your actual issue is. The 10ms latency is to do with synchronous replication. Network failure/recovery is handled with a different set of timers and counters. Please clarify.