Camunda not processing any flows and all are stuck at the initial stage

Hi Team,

We are using Camunda - 7.7.0 community version in our application. It is having some known issues, but all used to resolve when we restart camunda pod. But now we are facing an issue where all the flows are stuck at the beginning and there is no job executor running as per Camunda logs. All these flows work soon after restart but stops after 20 minutes. Nothing is written in logs and no jobs are progressing, even simple flows also stuck. We are using Mysql and deployed default camunda image. Any suggestion on how to resolve this would help.

Thanks

Can you format your question in a way thats a little easier to read :slight_smile:
Also - Camunda 7.7 is quite an old version the most recent is 7.14 - i’d suggest you upgrade and see if the problem persists.

Formatted :slight_smile: now it should be readable. We dont have provision to upgrade it.

Hi Niall,

Is there any way to progress the stuck process, can you suggest. It is just creating entry in ACT_RU_JOB table and retries count is 3.

Whenever process is stuck we are seeing only this in logs . Can anyone suggest on this please

01-Dec-2020 11:23:58.920 FINE [Thread-6] org.camunda.commons.logging.BaseLogger.logDebug ENGINE-14011 Job acquisition thread sleeping for 100 millis
01-Dec-2020 11:23:59.021 FINE [Thread-6] org.camunda.commons.logging.BaseLogger.logDebug ENGINE-14012 Job acquisition thread woke up
01-Dec-2020 11:23:59.021 FINE [Thread-6] org.camunda.commons.logging.BaseLogger.logDebug ENGINE-14022 Acquired 0 jobs for process engine ‘default’: []
01-Dec-2020 11:23:59.021 FINE [Thread-6] org.camunda.commons.logging.BaseLogger.logDebug ENGINE-14023 Execute jobs for process engine ‘default’: [ae1149f3-33c3-11eb-a0bd-565d562f3e7d]
01-Dec-2020 11:23:59.021 FINE [Thread-6] org.camunda.commons.logging.BaseLogger.logDebug ENGINE-14023 Execute jobs for process engine ‘default’: [f377b55f-33c3-11eb-a0bd-565d562f3e7d]
01-Dec-2020 11:23:59.021 FINE [Thread-6] org.camunda.commons.logging.BaseLogger.logDebug ENGINE-14023 Execute jobs for process engine ‘default’: [8a5e7f79-33c3-11eb-a0bd-565d562f3e7d]
01-Dec-2020 11:23:59.021 FINE [Thread-6] org.camunda.commons.logging.BaseLogger.logDebug ENGINE-14011 Job acquisition thread sleeping for 100 millis
01-Dec-2020 11:23:59.121 FINE [Thread-6] org.camunda.commons.logging.BaseLogger.logDebug ENGINE-14012 Job acquisition thread woke up
01-Dec-2020 11:23:59.122 FINE [Thread-6] org.camunda.commons.logging.BaseLogger.logDebug ENGINE-14022 Acquired 0 jobs for process engine ‘default’: []
01-Dec-2020 11:23:59.122 FINE [Thread-6] org.camunda.commons.logging.BaseLogger.logDebug ENGINE-14023 Execute jobs for process engine ‘default’: [ae1149f3-33c3-11eb-a0bd-565d562f3e7]

It’s going to be hard to help considering you’re using an unsupported version of the engine. 7.7 was released 3 years ago. What exactly is keeping you from upgrading to the new version?

Hi Niall,

` Thanks for your response. We need some approvals for upgrading and also we should give appropriate reason why we want to upgrade. Because from almost 3 years we are using this. Can you give some points where we can say in higher versions such issue will not occur.

I suggest to try to replicate the error locally and then upgrade the engine to the latest version and see it if still happens.