Null pointer exception on Startup | Community
Skip to main content
P
Pseuplex
June 2, 2022
Solved

Null pointer exception on Startup

  • June 2, 2022
  • 3 replies
  • 3964 views

Hey, 

 

When starting up AEM locally, I am getting a spam of 

 

java.lang.NullPointerException
at com.day.cq.dam.core.impl.process.SendTransientWorkflowCompletedEmailProcess.getEmailRecipients(SendTransientWorkflowCompletedEmailProcess.java:121)
at com.day.cq.dam.core.impl.process.SendTransientWorkflowCompletedEmailProcess.execute(SendTransientWorkflowCompletedEmailProcess.java:297)
at com.day.cq.workflow.compatibility.CQWorkflowProcessRunner.execute(CQWorkflowProcessRunner.java:93)
at com.adobe.granite.workflow.core.job.HandlerBase.executeProcess(HandlerBase.java:191)
at com.adobe.granite.workflow.core.job.JobHandler.process(JobHandler.java:260)
at org.apache.sling.event.impl.jobs.JobConsumerManager$JobConsumerWrapper.process(JobConsumerManager.java:502)
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl.startJob(JobQueueImpl.java:293)
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl.access$100(JobQueueImpl.java:60)
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl$1.run(JobQueueImpl.java:229)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)

 

It doesn't prevent me from accessing the site locally, but I can't seem to figure out why it's throwing this. I haven't run any workflows, I'm simply starting the application. It doesn't happen immediately, but after about 60 seconds, the terminal begins flooding. Any ideas on this? 

 

AEM Version: 6.5
Windows 10

Java 1.8

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Fanindra_Surat

Hi @pseuplex - Looks like you have a transient workflow running that is throwing an exception during an email send, and they don't leave a footprint to purge the running workflow instances.

You can proceed by looking for the transient workflows available in your instance, start them one by one and verify the logs to identify which one of them is throwing this exception and fix it accordingly.

 

Thanks,

Fani

3 replies

SantoshSai
Community Advisor
SantoshSaiCommunity Advisor
Community Advisor
June 2, 2022

Hi @pseuplex 

I see you are using Java 1.8. However, the recommended runtime environment for AEM 6.5 is Java 11.

Also worth checking

  1. Technical requirement: https://experienceleague.adobe.com/docs/experience-manager-65/deploying/introduction/technical-requirements.html?lang=en
  2. Setup AEM on local: https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/local-development-environment-set-up/aem-runtime.html?lang=en

If you follow relative steps correctly your AEM should be up and running.

Hope that helps!

Regards,
Santosh

Santosh Sai
    arunpatidar
    Community Advisor
    arunpatidarCommunity Advisor
    Community Advisor
    June 3, 2022

    Hi,

    Can you check if you have any workflow instances running or jobs are scheduled?

    You can check this from osgi console to know what events are happening and check the events logs also from osgi console

     

    Arun Patidar
      Fanindra_Surat
      Community Advisor
      Fanindra_SuratCommunity AdvisorAccepted solution
      Community Advisor
      June 3, 2022

      Hi @pseuplex - Looks like you have a transient workflow running that is throwing an exception during an email send, and they don't leave a footprint to purge the running workflow instances.

      You can proceed by looking for the transient workflows available in your instance, start them one by one and verify the logs to identify which one of them is throwing this exception and fix it accordingly.

       

      Thanks,

      Fani

        Terms & ConditionsAccessibility statement

        Loading footer...