Problem

When an automation rule with several webhooks has the option Wait for response before continuing ticked, Jira runs into an out of memory error.
When this option is ticked, Automation for Jira stores the webhook responses in a char[] array/string object. When there are enough webhook responses in one automation rule with this option selected, the size of the stored responses increases exponentially and eventually hits java's limit for string size, and ends up with an java.lang.OutOfMemoryError: Requested array size exceeds VM limit error.

Environment

Automation for Jira
Webhooks

Steps to Reproduce

1. Create an automation rule with a large amount of webhooks (30+ or more). The size of the webhook responses determine how early the OOME shows up.
2. Tick the Wait for response before continuing option.
3. Trigger the automation rule.

Expected Results

Automation rule completes successfully, triggering all webhooks.

Actual Results

Automation rule is terminated (at times doesn't get logged), and the java.lang.OutOfMemoryError: Requested array size exceeds VM limit shows up in the application logs.

Workaround

• Turn off the Wait for response before continuing when using an automation rule that triggers a large amount of webhooks
• Instead of one large automation rule with many webhooks, split it up into smaller automation rules with less webhooks each.
• As a preventive measure, you can search for A4J rules that make use of webhooks with the DB query below, and ensure that Wait for response before continuing is disabled for the rules that show up.

  select distinct a4jrule."NAME" from
          "AO_589059_RULE_CFG_COMPONENT" comp 
          join "AO_589059_RULE_CONFIG" a4jrule
                  on comp."RULE_CONFIG_ID" = a4jrule."ID" 
  where comp."TYPE" like '%webhook%';