High load conditions issue | Community
Skip to main content
A
AnujaRa
Level 2
June 15, 2025
Solved

High load conditions issue

  • June 15, 2025
  • 2 replies
  • 603 views

 

Hi everyone,

After upgrading to AEM 6.5.21, we noticed under high load conditions our author and publish instances intermittently throw exceptions like:

java.io.IOException: classFile.delete() failed  
java.io.IOException: tmpFile.renameTo(classFile) failed  
java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0  
java.io.FileNotFoundException

These errors reference the org.apache.sling.scripting.jsp:2.6.0 bundle.

Has anyone else experienced this?

Best answer by SantoshSai

Hi @anujara,

This is a documented known issue affecting AEM 6.5.21, 6.5.22, and 6.5.23.

The issue arises from a bug in the org.apache.sling.scripting.jsp:2.6.0 bundle, which under high concurrency can result in errors like:

  • IOException: classFile.delete() failed

  • ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0

  • FileNotFoundException

You can find this documented in the Release Notes for AEM 6.5 under the Known Issues section: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/release-notes/service-pack/6-5-21

Resolution:

This issue has been fixed in AEM 6.5.23, which addresses the JSP scripting bundle bug. Refer to the release notes here for confirmation:

  • 6.5.23 Service Pack Release Notes

2 replies

SantoshSai
Community Advisor
SantoshSaiCommunity AdvisorAccepted solution
Community Advisor
June 15, 2025

Hi @anujara,

This is a documented known issue affecting AEM 6.5.21, 6.5.22, and 6.5.23.

The issue arises from a bug in the org.apache.sling.scripting.jsp:2.6.0 bundle, which under high concurrency can result in errors like:

  • IOException: classFile.delete() failed

  • ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0

  • FileNotFoundException

You can find this documented in the Release Notes for AEM 6.5 under the Known Issues section: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/release-notes/service-pack/6-5-21

Resolution:

This issue has been fixed in AEM 6.5.23, which addresses the JSP scripting bundle bug. Refer to the release notes here for confirmation:

  • 6.5.23 Service Pack Release Notes

Santosh Sai
    A
    AnujaRaAuthor
    Level 2
    June 16, 2025

    @santoshsai Thanks - This make sense to me although, even after raising ticket to Adobe we receive the same suggestion.

      AmitVishwakarma
      Community Advisor
      AmitVishwakarmaCommunity Advisor
      Community Advisor
      June 16, 2025

      Hi @anujara ,

      Try below solution:

      Step 1: Upgrade to AEM 6.5.23 or 6.5.24

      Why:
      Adobe resolved this exact concurrency and file race condition bug in 6.5.23 with updated internal handling in the JSP compiler bundle.

      Step 2: (Optional If You Can't Upgrade) — Manual JSP Compiler Bundle Downgrade (Temporary Patch)

      If you can’t upgrade AEM due to release cycles or change control:

      Download Stable Older Version:

      Go to Apache Sling Repository and download:

      org.apache.sling.scripting.jsp-2.5.2.jar

      Uninstall the Faulty Bundle:

      org.apache.sling.scripting.jsp (2.6.0)

        - Go to /system/console/bundles

        - Stop and uninstall the 2.6.0 version.

       

      Upload and Install 2.5.2 Bundle

        - Use /system/console/install

        - Deploy org.apache.sling.scripting.jsp-2.5.2.jar

       

      This is NOT recommended for production long-term. Use it only as a temporary fix until proper upgrade.

       

      Step 3: Clear & Recompile JSP Cache (Once)

      After replacing the bundle or upgrading AEM

      Regards,
      Amit

        A
        AnujaRaAuthor
        Level 2
        June 16, 2025

        @amitvishwakarma I don't understand why you mentioned 6.5.21.0? My original question was "After upgrading to AEM 6.5.21..." not 6.5.23.

          Terms & ConditionsAccessibility statement

          Loading footer...