Expand my Community achievements bar.

Getting java.lang.NullPointerException: null \tat com.adobe.granite.workflow.core.job.JobHandler.process(JobHandler.java:403) after renaming asset from workflow

Avatar

Level 2

I have workflow which includes rename step and I am renaming an asset from xyz.png to abc.png as per business requirement but my workflow is getting triggered multiple times with following exception

com.adobe.granite.workflow.core.job.JobHandler Error executing workflow step
java.lang.NullPointerException: null
at com.adobe.granite.workflow.core.job.JobHandler.process(JobHandler.java:403) [com.adobe.granite.workflow.core:2.0.240.CQ658-B0017]
at org.apache.sling.event.impl.jobs.JobConsumerManager$JobConsumerWrapper.process(JobConsumerManager.java:502) [org.apache.sling.event:4.2.24]
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl.startJob(JobQueueImpl.java:351) [org.apache.sling.event:4.2.24]
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl.access$100(JobQueueImpl.java:60) [org.apache.sling.event:4.2.24]
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl$1.run(JobQueueImpl.java:287) [org.apache.sling.event:4.2.24]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
05.01.2024 19:45:02.646 *ERROR* [JobHandler: /var/workflow/instances/server0/2024-01-05/card-passbook-renditions_4:/content/dam/cards/ThankYouFY23_passbook_master.png/jcr:content/renditions/listenokkbosspassbook_master.png] com.adobe.granite.workflow.core.job.JobHandler Error processing workflow job
java.lang.NullPointerException: null
at com.adobe.granite.workflow.core.jcr.WorkflowManager.setWaitingToAdvance(WorkflowManager.java:562) [com.adobe.granite.workflow.core:2.0.240.CQ658-B0017]
at com.adobe.granite.workflow.core.job.JobHandler.process(JobHandler.java:431) [com.adobe.granite.workflow.core:2.0.240.CQ658-B0017]
at org.apache.sling.event.impl.jobs.JobConsumerManager$JobConsumerWrapper.process(JobConsumerManager.java:502) [org.apache.sling.event:4.2.24]
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl.startJob(JobQueueImpl.java:351) [org.apache.sling.event:4.2.24]
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl.access$100(JobQueueImpl.java:60) [org.apache.sling.event:4.2.24]
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl$1.run(JobQueueImpl.java:287) [org.apache.sling.event:4.2.24]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)

 

 

pawanpatilrocks_0-1704464732444.png

 

2 Replies

Avatar

Community Advisor

Here are a few suggestions to troubleshoot this issue:

  1. Workflow Step: Check if the issue is with the specific workflow step where the asset is being renamed. Try to isolate the problem by creating a simple workflow with just the rename step and see if the er....

  2. Asset: There might be something specific about the asset that’s causing the issue. Try renaming a different asset and see if you still encounter the error.

  3. Code Review: Review the code of your workflow step. The error message indicates that there’s a NullPointerException at JobHandler.process(JobHandler.java:403). This suggests that there might be an object that’s not been properly initialized.

  4. Apache Felix Console: Check in the Apache Felix console whether the process step component class is in active state or not. If you do not see the class listed then check the status of the OSGI bundle which contains this clas....

  5. Adobe Experience League Community: If you’re still unable to resolve the issue, consider reaching out to the Adobe Experience League Community. They might be able to provide more specific guidance or share experiences from similar projects.

Avatar

Level 2

Is this issue resolved if resolved please share the resolution for this issue. we are also facing the same issue.