cancel
Showing results for 
Search instead for 
Did you mean: 

CatalogVersionSyncJob waits for other cron jobs in WAITING state

Former Member
0 Kudos

Hi all,

We are invoking catalog version sync job programmatically to sync products from staged->online version, however we notice that the entire log is filled with these log messages where the sync job is randomly waiting for other cron jobs in UNKNOWN state to start. Has anyone encountered this situation before? Any pointers would be helpful.

INFO | jvm 1 | main | 2018/05/02 10:09:40.170 | WARN [000026PJ::de.hybris.platform.catalog.jalo.synchronization.CatalogVersionSyncJob] (000026PJ) [CatalogVersionSyncJob] Other cron job '00001RKK' (pk:8798792745461) is still in UNKNOWN state. Waiting '539' milliseconds for start INFO | jvm 1 | main | 2018/05/02 10:09:40.271 | WARN [000026PK::de.hybris.platform.catalog.jalo.synchronization.CatalogVersionSyncJob] (000026PK) [CatalogVersionSyncJob] Other cron job '00001QU7' (pk:8798761648629) is still in UNKNOWN state. Waiting '446' milliseconds for start INFO | jvm 1 | main | 2018/05/02 10:09:40.371 | WARN [000026PL::de.hybris.platform.catalog.jalo.synchronization.CatalogVersionSyncJob] (000026PL) [CatalogVersionSyncJob] Other cron job '00001PT3' (pk:8798717870581) is still in UNKNOWN state. Waiting '298' milliseconds for start INFO | jvm 1 | main | 2018/05/02 10:09:40.671 | WARN [000026PK::de.hybris.platform.catalog.jalo.synchronization.CatalogVersionSyncJob] (000026PK) [CatalogVersionSyncJob] Other cron job '00001QUO' (pk:8798762205685) is still in UNKNOWN state. Waiting '687' milliseconds for start INFO | jvm 1 | main | 2018/05/02 10:09:40.772 | WARN [000026PL::de.hybris.platform.catalog.jalo.synchronization.CatalogVersionSyncJob] (000026PL) [CatalogVersionSyncJob] Other cron job '00001PT4' (pk:8798717903349) is still in UNKNOWN state. Waiting '827' milliseconds for start INFO | jvm 1 | main | 2018/05/02 10:09:40.772 | WARN [000026PJ::de.hybris.platform.catalog.jalo.synchronization.CatalogVersionSyncJob] (000026PJ) [CatalogVersionSyncJob] Other cron job '00001RKY' (pk:8798793204213) is still in UNKNOWN state. Waiting '1085' milliseconds for start INFO | jvm 1 | main | 2018/05/02 10:09:40.972 | WARN [000026PM::de.hybris.platform.catalog.jalo.synchronization.CatalogVersionSyncJob] (000026PM) [CatalogVersionSyncJob] Other cron job '00001PRW' (pk:8798716461557) is still in UNKNOWN state. Waiting '639' milliseconds for start

Accepted Solutions (0)

Answers (3)

Answers (3)

priyanka_gupta2692
Participant
0 Kudos

Delete All cronjobs which are still in UNKNOWN state. Then start your cronjob again. It will resolve the issue

0 Kudos

Hi all,

I am invoking syncronization jobs to sync product catalogs from staged -> online version and I am getting the same messages as in the answer. Has anyone managed to figure out how this one could be resolved ? What is causing Sync Jobs to wait for other jobs to finish in UNKNOWN state ?

WARN [TaskExecutor-master-89256-TriggerTask [8799566529462]] [CatalogVersionSyncJob] Other cron job '0000H2BX' (pk:8822182052341) is still in UNKNOWN state. Waiting '1065' milliseconds for start

WARN [TaskExecutor-master-89256-TriggerTask [8799566529462]] [CatalogVersionSyncJob] Other cron job '0000H31B' (pk:8822211969525) is still in UNKNOWN state. Waiting '1053' milliseconds for start

WARN [TaskExecutor-master-89256-TriggerTask [8799566529462]] [CatalogVersionSyncJob] Other cron job '0000H2C7' (pk:8822182380021) is still in UNKNOWN state. Waiting '604' milliseconds for start

WARN [TaskExecutor-master-89256-TriggerTask [8799566529462]] [CatalogVersionSyncJob] Other cron job '0000H2C9' (pk:8822182412789) is still in UNKNOWN state. Waiting '286' milliseconds for start

WARN [TaskExecutor-master-89256-TriggerTask [8799566529462]] [CatalogVersionSyncJob] Other cron job '0000H31F' (pk:8822212166133) is still in UNKNOWN state. Waiting '526' milliseconds for start

WARN [TaskExecutor-master-89256-TriggerTask [8799566529462]] [CatalogVersionSyncJob] Other cron job '0000H2CL' (pk:8822182838773) is still in UNKNOWN state. Waiting '1142' milliseconds for start

Former Member
0 Kudos

We've recently run into the same issue. Remove the catalogVersionSyncJobs that were automatically created before and left in state unknown, and the synchronization will work.