Technically the message is not "staying" on the queue - its being processed to the n-th degree (have a look at the backout count in the message headers on MQ. To avoid this, ensure that your MQ queue backout count and backout queue has been set.
Understanding MQ Backout Queues & Thresholds (ibm.com)
Backout count - IBM Documentation
However, to avoid a lot of frustration in future, linking your catch and failure terminal as Khalid said is the best solution.
------------------------------
Heidi-Lize Scholtz
------------------------------
Original Message:
Sent: Tue February 27, 2024 07:42 AM
From: Khalid Hasan
Subject: MQInput node stopped reading message from input queue
Hi,
The issue is that when an error happens at any node on the flow (and there is no error handling set for this error), the message returned to the MQInput node which rolls back the get action and the message is kept in the MQ queue. All this is not captured with the debugger.
The solution is to wire the catch and failure output termicals for all nodes and route them to error handling route in the flow. This way, the error will not bounce back to MQInput node.
Best regards,
------------------------------
Khalid Hasan
Original Message:
Sent: Mon February 26, 2024 05:22 PM
From: Elizabeth Zarate
Subject: MQInput node stopped reading message from input queue
Hi, we are using ace-12.0.5.0 version and we have the same issue.
Anybody seen the same issue?
and if somebody solved it, can share us the steps, please?
Thanks in advance
------------------------------
Elizabeth Zarate
Original Message:
Sent: Mon February 26, 2024 07:25 AM
From: خالد حسن
Subject: MQInput node stopped reading message from input queue
After successfuly created a work flow and read message from MQ input queue usin MQInput node. It stopped reading new messages from the input queue without any errors.
------------------------------
خالد حسن
------------------------------