java.io.IOException: classFile.delete() failed

[akhilraj]

Hi,

One of our production publishers failed with 500 internal errors.

Upon checking the logs we found below:

org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException

java.io.IOException: classFile.delete() failed

 This particular issue was resolved automatically after 10 minutes, but still we restarted the instances.

.

What could be the possible root cause of this, and what actions can we take to prevent the recurrence of this issue?

[SureshDhulipudi]

Is this happening only in production instances?, are you able to replicate this issue in lower environment.

Please raise a Support ticket with AMS (adobe managed services) to check with their engineering team.

[akhilraj]

It happened only  once in one of the Prod publisher and issue resolved automatically within 5 min.

We have raised with Adobe now

[BrianKasingli]

I had this problem on one of our onPrem publish environments before, like back in 2021

We found out that it was related to AEM’s Java class generation (e.g., scripts, components, or HTL templates compiled to Java files). When these class files cannot be deleted properly, it may cause errors, especially under high traffic or during deployments.

How we solved it:

• Check Error Logs for Compilation Errors: Investigate the logs further to identify whether specific components or scripts failed to compile and generate the class files.

  Look for issues related to HTL (HTML Template Language) or JSP files.

• Clear Sling Cache: AEM caches compiled scripts and components, and sometimes clearing this cache can resolve the issue.

  •  You can manually clear the Sling Script Cache by navigating to:
    /system/console/slingjsp
  • Click on "Clear JSP Script Cache" to force recompilation of the files.

  • Check the Temporary Directory: Look into the AEM temporary directory (/tmp/aem-cache, /crx-quickstart/tmp, etc.) for any issues with leftover files or a full directory.

It was not 100% understandable for why this happened, but we decided to update the latest AEM service pack, and this problem did not surface anymore.

[IanSm1]

We had the same issue on one of our Prod publishers on SP21. Clearing the JSP cache worked for us as well. I must however mention that the URL to clear it has been changed to /system/console/fsclassloader.

[Jörg_Hoh]

Is this AEM 6.5 SP21?

[akhilraj]

Yes, we have recently upgraded SP to 21

[keith_howe]

We also have a client that has begun experiencing this issue on an AEM production publish instance since updating to AEM 6.5 SP21.

[akhilraj]

Hi @keith_howe ,

Did you get any root cause of the issue? Any action you have taken to resolve the same?

[keith_howe]

We did not definitively identify a root-cause yet but we have more gracefully handled some run-time compilation errors in several components in hopes that would help.

[akhilraj]

Hi @Jörg_Hoh ,

Do you expect any issue with SP 21?

[Jörg_Hoh]

I just heard from colleagues about a very similar problem (maybe the same?) with AEM 6.5 SP21.

Please report it to Adobe support, but I think that a bugfix is already on its way.

[akhilraj]

Hi @Jörg_Hoh ,

Is there any way, we can get confirmation on the same, so that I can discuss it internally with our team and upgrade the latest SP with the bugfix once they are available

[kautuk_sahni]

@akhilraj Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

[akhilraj · Accepted solution]

Hi Everyone, Below is the update received from Adobe.

[akhilraj]

I am unable to mark it as correct answer, not see the option