Hello community team!
We use CA API Gateway 9.3 CR4 as cluster from two nodes. We have problems with MQ Native Queue Inbound functionality. We have two scenarios how we use it:
1. Both nodes are active/active and connected to a remote endpoint(MQ Server). MQ messages come randomly, sometimes one per month. MQ Native Queue Inbound looks still active but the messages don't proceed. We don't have any error messages about problems with processing of this waiting messages.
2. One of the cluster nodes is active and the second one is passive. Passive node generates every 5 seconds error message about communication problems - that is the correct state. But the active node behaves like nodes described in the first scenario.
Our problem is with a "Test Settings" button. When we push this button from active node, result is always OK. But in the background the messages on remote MQ Server aren't processed, although VPN tunnel to remote MQ server is still active.
Any ideas how to set some Cluster-Wide Properties parameters(which have an influence on getting to idle state?) Or how to set detailed logging? Or anything else?
Thank you in advance!
It believe it would be better if you open a support ticket for this specific issue, so that we can analyse the settings you currently have and how they can/should be adjusted.
There are several cluster properties, that might be connected (see https://docops.ca.com/ca-api-gateway/9-4/en/reference/gateway-cluster-properties/input-output-cluster-properties)