MuleSoft · Anypoint MQ Connector
ANYPOINT-MQ:TIMEOUT
Short answer
ANYPOINT-MQ:TIMEOUT is thrown by the Consume operation when Polling Time is greater than 0 and no message arrives in that time. If an empty queue is normal, handle the error or set Polling Time to 0, which returns NULL instead.
VerifiedLast verified
01Error text
Error type: ANYPOINT-MQ:TIMEOUT02Likely causes
- The Consume operation's Polling Time is greater than 0 and no message arrived before it elapsed. The default is 10000 milliseconds, and the allowed range is 0 to 20000.
03How to fix it
- Decide whether an empty queue is an error for this flow.
- If it is not, set Polling Time to
0. The connector then returnsNULLand does not throwANYPOINT-MQ:TIMEOUT. - Or keep the polling time and handle the failure with an error handler of type
ANYPOINT-MQ:TIMEOUT.
04Official documentation
→Related errors
- VM:QUEUE_TIMEOUTVM:QUEUE_TIMEOUT means a VM Connector operation waited for a queue longer than its Timeout, which is 5 seconds by default. Raise the Timeout, or make the flow that consumes the queue finish sooner.
- JMS:TIMEOUTJMS:TIMEOUT means the timeout for the requested JMS operation was exceeded. Check why the broker or the replying party did not answer in time before raising the timeout.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer