ConnectALL 3.9.2 - Records failed due to Jira rate limit not processed like previous version but with the added issue that the automation has stopped processing

Products

• ConnectAll On-Prem
• ConnectALL

Issue/Introduction

There was a defect where records failed due to rate limit were not being retried. The issue was fixed in ConnectALL 3.9.2 but since the upgrade to this version, ConnectALL still does not process all records failed due to rate limit.

 

Steps to Reproduce: 

1. Upgrade to 3.9.2
2. Try to sync 1000+ records from Jira to Rally

 

Actual Results: 
Automation won't retry all records when records failed with rate limit error.

 

Expected Results: 
Automation should sync or add records failed due to rate limit to retry queue and process it in subsequent run when cooling period is crossed.

Environment

3.9.2

Cause

DE178559

Resolution

DE178559 is fixed in patch 4.0.1


Workaround:

Configuration changes below on top of ConnectALL 3.9.2

Add below configuration in ..Core/conf/application.properties.

# Configure SEDA queues to block producers when full. This prevents message loss
# under high load at the cost of potential producer thread blocking.
camel.component.seda.default-block-when-full=true