MuleSoft · VM Connector
VM:QUEUE_TIMEOUT
Short answer
VM: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.
VerifiedLast verified
01Error text
Error type: VM:QUEUE_TIMEOUT02Likely causes
- The operation waited for the queue to complete a publish or a consume for longer than the configured Timeout. The default is 5 seconds.
- Publish Consume waits up to that time for a response, and the flow that listens on the queue did not reply in time.
- Consume waited that long on a queue that received no message.
03How to fix it
- Find which operation raised the error: Publish, Publish Consume or Consume.
- For Publish Consume, measure how long the listening flow takes to reply, and shorten its work if you can.
- Raise Timeout and Timeout Unit on the operation to cover the real processing time.
- Handle the failure with an error handler of type
VM:QUEUE_TIMEOUT.
04Official documentation
→Related errors
- HTTP:TIMEOUTHTTP:TIMEOUT means a request sent by the HTTP Request operation timed out before the response arrived. The wait is set by Response Timeout, which is 10000 milliseconds unless you change it, so raise it or make the remote service answer faster.
- MULE:RETRY_EXHAUSTEDMULE:RETRY_EXHAUSTED means every retry of an execution block failed, most often an Until Successful scope whose final retry did not succeed. Fix the error that the processors inside the scope keep raising, or adjust maxRetries and millisBetweenRetries.
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