ConnectALL Automations will not run
search cancel

ConnectALL Automations will not run

book

Article ID: 369900

calendar_today

Updated On: 01-15-2025

Products

ConnectALL ConnectAll On-Prem ConnectAll SaaS

Issue/Introduction

Automations are not running or acquiring a lock.  The automation log file is repeating the following message every few seconds:

WARN  yyyy-MM-DD HH:mm:ss,SSS [<Automation Name> | <Automation Timestamp> |  | {<Project<}][(connectall-flows) thread #nnnn - Split] org.apache.activemq.artemis.core.client: AMQ212054: Destination address=writeQ is blocked. If the system is configured to block make sure you consume messages on this configuration.

 

Or the Artmeis logs may show the following

yyyy-MM-DD HH:mm:ss,SSS WARN  [org.apache.activemq.artemis.core.server] AMQ222210: Free storage space is at 10.1GB of 107.0GB total. Usage rate is 90.5% which is beyond the configured <max-disk-usage>. System will start blocking producers.
yyyy-MM-DD HH:mm:ss,SSS WARN  [org.apache.activemq.artemis.core.server] AMQ222212: Disk Full! Blocking message production on address 'jobQ'. Clients will report blocked.
yyyy-MM-DD HH:mm:ss,SSS WARN  [org.apache.activemq.artemis.core.server] AMQ222212: Disk Full! Blocking message production on address 'readQ'. Clients will report blocked.

Cause

This can be caused if disk space usage rises above the configured disk space threshold in the broker service; by default this is 90%.

Resolution

There are two options to resolve this. 

1) Clear disk space until the used space falls below 90%

 

2) Reconfigure the broker service disk threshold to a higher value

To do this, edit <CONNECTALL_HOME>/Broker/connectall-broker/etc/broker.xml

Locate the line that reads <max-disk-usage>90</max-disk-usage>

Change 90 to a higher value

Save and restart the broker service

Additional Information

Note: Some services do not recover from a low disk event, and it is advisable to restart all services, or restart the machine in order to ensure the application is operating from a known good position prior to troubleshooting any further issues.