AnsweredAssumed Answered

What triggers upgrading activiti history 5.13 to 5.11?

Question asked by houstoniasian on Oct 22, 2013
Latest reply on Oct 23, 2013 by houstoniasian
All I did was to instantiate processEngine:  processEngine = ProcessEngines.getDefaultProcessEngine();

In the console, I see these lines:

Oct 22, 2013 3:05:20 PM org.activiti.engine.ProcessEngines init
INFO: Initializing process engine using configuration 'file:/C:/Users/Acer%20User/workspace/Activiti-Stock/target/classes/activiti.cfg.xml'
Oct 22, 2013 3:05:21 PM org.activiti.engine.ProcessEngines initProcessEnginFromResource
INFO: initializing process engine for resource file:/C:/Users/Acer%20User/workspace/Activiti-Stock/target/classes/activiti.cfg.xml
Oct 22, 2013 3:05:21 PM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions
INFO: Loading XML bean definitions from resource loaded through InputStream
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Oct 22, 2013 3:05:23 PM org.activiti.engine.impl.db.DbSqlSession dbSchemaUpgrade
INFO: upgrading activiti engine schema from 5.13 to 5.11
Oct 22, 2013 3:05:23 PM org.activiti.engine.impl.db.DbSqlSession dbSchemaUpgrade
INFO: upgrading activiti history schema from 5.13 to 5.11
Oct 22, 2013 3:05:23 PM org.activiti.engine.impl.db.DbSqlSession dbSchemaUpgrade
INFO: upgrading activiti identity schema from 5.13 to 5.11

Why on earth Activiti upgrade the schema from 5.13 to 5.11?  So I go to the table act_ge_property, change it back to 5.13, the next time I run, it upgrade from 5.13 to 5.11 again.  This really screw my program up as for some reasons, if I start Tomcat and the schema.version is 5.11, then will get upgrading error.

How can I fix this?

Tan

Outcomes