Hello,
We are facing a major issue with MQInput Node which is used to read messages from remote MQ and transfer to BAW.
Scenario:
1. We have an IBM MQ Queue which is holding lot of messages which are piled up and expected to be read from IBM AppConnect.
2. We are deploying IBM ACE flow using Jenkins Pipeline over RHEL OCP 4.10 CP4I container environment.
Problem Statement:
As soon as Jenkins job is triggered to deploy IBM ACE project to OCP environment, it establishes MQ connection while the pod state shows as Running but not in 1/1 Ready State instead it is still coming up.
During this time when the pod is still not READY, premature ACE flow gets triggered which in turn results in losing MQ messages as ACE flow is still not ready to process the messages further.
Once the pod is in READY state, rest of MQ messages are processed successfully by ACE flow pod.
To conclude, how to fix this issue of premature ACE flow execution even before ACE pod moves into READY state.
Do we have any IdleTimeOut property which can be used over MQInputNode to delay processing of MQ messages until POD state is READY.
This is a business blocker issue reported for one of the critical insurance application to replace legacy IBM SCA module to IBM ACE.
We need urgent resolution for the issue.
Thanks.
------------------------------
Abhishek Mittal
------------------------------