Loading

Anypoint MQ messages not consumed for a very long time with error Notify Circuit ERROR: UNKNOWN in logs

Udgivelsesdato: Jul 23, 2025
Løsning

SYMPTOM

Anypoint MQ subscriber with the circuit breaker is stuck and not subscribing to the messages pushed in MQ.
Below error messages are observed in log -  
[processor: ; event: f0e49090-3640-11eb-be5f-f01898543f0c] com.mulesoft.extension.mq.internal.source.AnypointMQSource: Notify Circuit ERROR: UNKNOWN
DEBUG 2020-12-04 08:57:20,970 [[MuleRuntime].uber.12: [mqreproduce].job-errors/0/processors/3.ps.CPU_LITE @f3e9e4e]
 [processor: ; event: f0e49090-3640-11eb-be5f-f01898543f0c] 
com.mulesoft.extension.mq.internal.source.AnypointMQSource: Error Cause: 'UNKNOWN' - Error was 'null'
DEBUG 2020-12-04 08:57:21,106 [pool-14-thread-1] [processor: ; event: ] com.mulesoft.mq.restclient.internal.ScheduledPrefetcher: Already 1 request in progress, skipping message fetch for test
DEBUG 2020-12-04 08:57:26,109 [pool-14-thread-1] [processor: ; event: ] com.mulesoft.mq.restclient.internal.ScheduledPrefetcher: Already 1 request in progress, skipping message fetch for test
DEBUG 2020-12-04 08:57:31,106 [pool-14-thread-1] [processor: ; event: ] com.mulesoft.mq.restclient.internal.ScheduledPrefetcher: Already 1 request in progress, skipping message fetch for test
DEBUG 2020-12-04 08:57:31,235 [pool-15-thread-1] [processor: ; event: ] com.mulesoft.mq.restclient.internal.SimpleBufferedQueue: Polling message from buffer with timeout of 20000 MILLIS
DEBUG 2020-12-04 08:57:36,106 [pool-14-thread-1] [processor: ; event: ] com.mulesoft.mq.restclient.internal.ScheduledPrefetcher: Already 1 request in progress, skipping message fetch for test
DEBUG 2020-12-04 08:57:41,106 [pool-14-thread-1] [processor: ; event: ] com.mulesoft.mq.restclient.internal.ScheduledPrefetcher: Already 1 request in progress, skipping message fetch for test

It does not subscribe to the messages even after the time defined in Circuit Breaker - 
circuit breaker

CAUSE

This is a bug in Anypoint MQ Connector version 3.1.1

SOLUTION

This bug is fixed in the 3.1.2 version of the MQ connector. Below are the release notes - 
https://docs.mulesoft.com/release-notes/connector/anypoint-mq-connector-release-notes-mule-4#3-1-2
Please update the connector version to get the bug fix.
 
Vidensartikelnummer

001120518

 
Indlæser
Salesforce Help | Article