Severe error on engine log when disabling history

Ghassen_Trabelsi · March 14, 2020, 9:31pm

Hi,

We are seeing a severe error on Camunda engine logs on each startup:
14-Mar-2020 22:19:51.693 SEVERE [main] org.camunda.commons.logging.BaseLogger.logError ENGINE-16004 Exception while closing command context: ENGINE-03053 History is not enabled. org.camunda.bpm.engine.ProcessEngineException: ENGINE-03053 History is not enabled. at org.camunda.bpm.engine.impl.db.EnginePersistenceLogger.disabledHistoryException(EnginePersistenceLogger.java:465) at org.camunda.bpm.engine.impl.persistence.AbstractHistoricManager.checkHistoryEnabled(AbstractHistoricManager.java:39) at org.camunda.bpm.engine.impl.persistence.entity.CommentManager.insert(CommentManager.java:46

The error appears only when we history is disabled:
<property name="history">none</property>

Any clue why this error is raised ?

Ingo_Richtsmeier · March 16, 2020, 8:37am

Hi @Ghassen_Trabelsi,

maybe this thread could help you: Changing History Level on Existing Camunda Installation.

Hope this helps, Ingo

Ghassen_Trabelsi · March 24, 2020, 12:45pm

Hi @Ingo_Richtsmeier
We actually followed the example you mentioned. The error I mentioned is not blocking the engine from working. Everything is working fine and history is correctly disabled but still the error appear at startup (only once). we only want to mention that there is an error message on engine log when disabling the history.