AnsweredAssumed Answered

changing the historyLevel

Question asked by heymjo on May 3, 2012
Latest reply on May 3, 2012 by heymjo

An application is running activiti with historyLevel set to the default 'full'. When the application now wants to change the historyLevel to the default 'audit' it is not enough to make the change on the process engine configuration, you get this error:

<03-May-2012 11:50:23 o'clock CEST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: :org.activiti.engine.ActivitiException:Activiti database problem: historyLevel mismatch: configuration says 2 and database says 3

When i then do

UPDATE act_ge_property SET value_ = 2 WHERE name_ = 'historyLevel'

it works again.

Why is the historyLevel hardcoded in the database ? AFAICT it is only the engine that writes to the history tables, and that engine is configured on the java level already so no need to go and check against a configuration table.

Thoughts ?