nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Activit Engine 5.7 auto downgrades to 5.6 then fails

davidwaf

Hi all,
am not sure where am going wrong, my app is using 5.7. Which worked fine, until i restarted tomcat. Am using spring with the following config:

<!– Configure process engine –>
    <bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration"
      lazy-init="true">
        <property name="databaseType" value="mysql" />
        <property name="dataSource" ref="dataSource" />
        <property name="transactionManager" ref="transactionManager" />
        <property name="databaseSchemaUpdate" value="true" />
        <property name="jobExecutorActivate" value="false" />
    </bean>
‍‍‍‍‍‍‍‍‍‍‍

when restarting tomcat, i see this in the logs:

19 Aug 2011 12:33:28 PM org.activiti.engine.impl.db.DbSqlSession dbSchemaUpgrade
INFO: upgrading activiti engine schema from 5.7 to 5.6
‍‍‍‍

This looks suspicious to me.
Which then results in

INFO: upgrading activiti engine schema from 5.6 to 5.7
19 Aug 2011 12:33:38 PM org.activiti.engine.impl.db.DbSqlSession dbSchemaUpgrade
INFO: upgrading activiti history schema from 5.6 to 5.7
19 Aug 2011 12:33:38 PM org.activiti.engine.impl.db.DbSqlSession executeSchemaResource
INFO: performing upgrade on history with resource org/activiti/db/upgrade/activiti.mysql.upgradestep.56.to.57.history.sql
19 Aug 2011 12:33:38 PM org.activiti.engine.impl.db.DbSqlSession executeSchemaResource
SEVERE: problem during schema upgrade, statement 'alter table ACT_HI_PROCINST 
add SUPER_PROCESS_INSTANCE_ID_ varchar(64)
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column name 'SUPER_PROCESS_INSTANCE_ID_'

‍‍‍‍‍‍‍‍‍‍‍‍

Am not sure why it is 'upgrading' from 5.7 to 5.6 when i restart tomcat.
Cheers.

Find more posts tagged with

Comments

gant

Hi,

Do you have both versions 5.6 and 5.7 of activiti-engine.jar on your classpath? I had this and after cleaning the dependencies, it all worked fine.

Regards

davidwaf

It turns out i had another webapp using 5.6 that was in same container, and was loading first, but (stupid me) sharing same database. Fixed this, all is ok now. Thanks.

frederikherema1

The 'upgrading' log is shown even before checking if any steps are required. In case of a downgrade, nothing is done… So the 5.6 to 5.7 can be ignored.