SAP Knowledge Base Article - Preview

3398833 - Cronjob is not running due to null session attribute

Symptom

Cronjob is not running and Kibana shows logs like:

ERROR [indexer-backoffice-product-full::de.hybris.platform.servicelayer.internal.jalo.ServicelayerJob] (indexer-backoffice-product-full) [Job] Could not start own session due to Session attribute for cronjob 'indexer-backoffice-product-full' were null! [user:null, currency:8796093087777->EUR, language:8796093055008->en
de.hybris.platform.jalo.ConsistencyCheckException: Session attribute for cronjob 'indexer-backoffice-product-full' were null! [user:null, currency:8796093087777->EUR, language:8796093055008->en[HY-0]
    at de.hybris.platform.cronjob.jalo.Job.startOwnSession(Job.java:1287)
    at de.hybris.platform.cronjob.jalo.Job.performImpl(Job.java:782)
    at de.hybris.platform.cronjob.jalo.Job$JobRunable.run(Job.java:688)
    at de.hybris.platform.util.threadpool.PoolableThread.internalRun(PoolableThread.java:204)
    at de.hybris.platform.core.threadregistry.RegistrableThread.run(RegistrableThread.java:124)
Caused by: java.lang.IllegalStateException: Session attribute for cronjob 'indexer-backoffice-product-full' were null! [user:null, currency:8796093087777->EUR, language:8796093055008->en
    at de.hybris.platform.cronjob.jalo.CronJob.createSessionForCronJob(CronJob.java:2056)
    at de.hybris.platform.cronjob.jalo.Job.startOwnSession(Job.java:1283)
    ... 4 more

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."


Read more...

Environment

SAP Commerce Cloud

Product

SAP Commerce Cloud all versions

Keywords

KBA , CEC-SCC-PLA-PL , Platform , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.