You have set the MQGET node to browse only, not do a destructive get. What is the queue depth at the times where the wait is long?
This set up can make for some interesting queue depths. Do you have an expiration set on the queue or the messages to avoid the queue getting too deep?
Even though the MQGET is being done by correlation ID, loading a deep queue into the catalog still takes time and may be one of the reasons you see those delays.
If the queue is used unfrequently at night time, it may be dropped from the catalog and when you do need to make the next get, will have to be reloaded into the catalog.
With deep queues this reload time is not trivial.
------------------------------
Francois Brandelik
------------------------------
Original Message:
Sent: Wed August 04, 2021 02:50 AM
From: Vishwanath Dubey
Subject: Issue on MQGET Node wait interval time
Hi,
We are having issue for receiving message from an external entity where we have used MQGet Node.
Though we have set "wait interval time" for 1 sec (1000ms), it does not work, and wait upto 30-40 secs [some time it reaches to 200 sec]
The problem is happening at a particular time interval [at night time], otherwise ACE flow return response back to consumer within 1 sec (1000 milisec), irrespective of response has received or not received from Fiserv. and
in later case If response is not received within 1 sec, it sends back correlation id to consumer with HTTP 202,
otherwise send response from Fiserv with HTTP 200
Kindly refer the attachment where MQGET node properties are specified.
You response is highly awaited
Thanks & Regards,
Vishwanath
------------------------------
Vishwanath Dubey
------------------------------