WebRunner is unreachable when saving the Data Mapping

Summary

In Adeptia Connect 4.6, users may encounter repeated WebRunner restarts when attempting to copy or save large data mappings. The issue is reproducible, particularly with complex mappings that contain large rule sets or lengthy string operations.

Problems Occur when we Validate the issue

When copying or saving a large mapping:

• UI displays: "WebRunner is not reachable"

• Operation fails part-way through

• WebRunner pod restarts automatically

• WebRunner logs do not show a specific error

• Kubernetes Dashboard shows 100% memory utilization at the time of failure

Root Cause

AC 4.6 introduced an update to the file: xsl format

Adp_Map_Rules.xsl

Specifically, the following line was added (line 9):

<xsl:value-of select="replace($input,'([0-9_a-zA-Z]{3})','$1&#8203;')"/>

Why this causes issues:

• This expression inserts a zero-width space (​) after every 3 characters in all mapping rules.

• For large mappings with large rule bodies, this transformation expands strings exponentially.

   This results in:

• Heavy XSLT processing load

• Excessive Java heap consumption

• WebRunner memory spike to 100%

• Pod restart by Kubernetes

This transformation did not exist in AC 4.4, which is why the same mappings save and copy successfully there.

Impact

• Large/complex Data Mappings fail during save/copy operations.

• WebRunner becomes unstable under normal workload.

• Migration or editing of existing mappings becomes difficult in AC 4.6.

Resolution

Modify Adp_Map_Rules.xsl in the WebRunner container to remove the costly regex-based string processing.

Steps

1. Open a shell into the WebRunner pod.

2. Navigate to the XSL location (path may vary based on deployment):

/opt/adeptia/…/webrunner/…/Adp_Map_Rules.xsl

Locate line 9:

<xsl:value-of select="replace($input,'([0-9_a-zA-Z]{3})','$1&#8203;')"/>

4. Replace it with:

<xsl:value-of select="$input"/>

1. 

   Save the file and restart WebRunner (if required by deployment).

    

Validation

After applying the fix:

• Copying “SL_DM_MergeAndValidation(Mapping)” completes successfully

• No memory spike observed

• No WebRunner restarts

• Behavior matches AC 4.4 performance

Adeptia Support validated the fix in local AC 4.6, AC4 Tech-Support environment, and customer-provided mappings. 

provided the sample xsl file changes were included in the file accordingly 

Workaround

• Temporarily increase WebRunner pod memory (e.g., 8Gi → 12–16Gi)
  (Not recommended as a long-term solution)