Несовпадение уровней истории на Camunda 7.2

Question

Я развернул camunda.war (7.2) в своей ванильной tomcat7, следуя инструкциям на официальном сайте.

Теперь, когда я запускаю Tomcat, у меня появляется следующая ошибка:

GRAVE: Error while closing command context
org.camunda.bpm.engine.ProcessEngineException: historyLevel mismatch: configuration says org.camunda.bpm.engine.impl.history.HistoryLevelAudit@21 and database says 3

В базе данных (таблица ACT_GE_PROPERTY) historyLevel установлен в 3, это мой файл bpm-platform.xml

    <?xml version="1.0" encoding="UTF-8"?>
<bpm-platform xmlns="http://www.camunda.org/schema/1.0/BpmPlatform"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.camunda.org/schema/1.0/BpmPlatform http://www.camunda.org/schema/1.0/BpmPlatform ">

  <job-executor>
    <job-acquisition name="default" />
  </job-executor>

  <process-engine name="default">
    <job-acquisition>default</job-acquisition>
    <configuration>org.camunda.bpm.engine.impl.cfg.StandaloneProcessEngineConfiguration</configuration>
    <datasource>java:jdbc/solve</datasource> 

    <properties>
      <property name="history">full</property>
      <property name="databaseSchemaUpdate">true</property>
      <property name="authorizationEnabled">true</property>
      <property name="jobExecutorDeploymentAware">true</property>
    </properties>


    <plugins>

    <!-- plugin enabling Process Application event listener support -->
        <plugin>
           <class>org.camunda.bpm.application.impl.event.ProcessApplicationEventListenerPlugin</class>
        </plugin>

    <!-- plugin enabling integration of camunda Spin -->
        <plugin>
           <class>org.camunda.spin.plugin.impl.SpinProcessEnginePlugin</class>
        </plugin>

        <!-- plugin enabling connect support -->
        <plugin>
           <class>org.camunda.connect.plugin.impl.ConnectProcessEnginePlugin</class>
        </plugin>
    </plugins>

  </process-engine>

</bpm-platform>

РЕДАКТИРОВАТЬ

Processes.xml

    <?xml version="1.0" encoding="UTF-8" ?> 
<process-application 
     xmlns="http://www.camunda.org/schema/1.0/ProcessApplication" 
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 

  <process-archive name="MyProcess"> 
    <process-engine>myEngine</process-engine>
    <properties> 
      <property name="isDeleteUponUndeploy">false</property> 
      <property name="isScanForProcessDefinitions">true</property> 
    </properties> 
  </process-archive> 

</process-application>

applicationContext.xml

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:context="http://www.springframework.org/schema/context"
    xmlns:tx="http://www.springframework.org/schema/tx" xmlns:jee="http://www.springframework.org/schema/jee"
    xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.1.xsd
       http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.1.xsd
       http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.1.xsd
       http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-3.1.xsd">


    <jee:jndi-lookup id="dataSource" jndi-name="java:comp/env/jdbc/my_process" />

    <bean id="transactionManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
        <property name="dataSource" ref="dataSource" />
    </bean>

    <bean id="processEngineConfiguration" class="org.camunda.bpm.engine.spring.SpringProcessEngineConfiguration">
        <property name="processEngineName" value="myEngine" /> 
        <property name="dataSource" ref="dataSource" />
        <property name="transactionManager" ref="transactionManager" />
        <property name="databaseSchemaUpdate" value="true" />
        <property name="jobExecutorActivate" value="false" />
        <property name="deploymentResources" value="classpath*:*.bpmn" />
        <property name="processEnginePlugins">
            <list>
              <bean id="spinPlugin" class="org.camunda.spin.plugin.impl.SpinProcessEnginePlugin" />
            </list>
        </property>
    </bean>

    <bean id="processEngine" class="org.camunda.bpm.engine.spring.container.ManagedProcessEngineFactoryBean" destroy-method="destroy">
        <property name="processEngineConfiguration" ref="processEngineConfiguration" />
    </bean>

    <bean id="repositoryService" factory-bean="processEngine" factory-method="getRepositoryService" />
    <bean id="runtimeService" factory-bean="processEngine" factory-method="getRuntimeService" />
    <bean id="taskService" factory-bean="processEngine" factory-method="getTaskService" />
    <bean id="historyService" factory-bean="processEngine" factory-method="getHistoryService" />
    <bean id="managementService" factory-bean="processEngine" factory-method="getManagementService" />

    <bean id="MyProcess" class="org.camunda.bpm.engine.spring.application.SpringServletProcessApplication" />

    <context:annotation-config />

    <bean class="it.processes.Starter" />
    <bean id="cudOnProcessVariableService" class="it.services.CUDonProcessVariableService" />

</beans>

Answer 1

Вы загружали WAR-файл 'Camunda Standalone WebApp' для Tomcat с веб-сайта camunda.org/download?

Если это так, вы должны отрегулировать уровень истории внутри файла application-context.xml, добавив <property name="history" value="full"/> к бину конфигурации двигателя процесса <bean id="processEngineConfiguration" class="org.camunda.bpm.engine.spring.SpringProcessEngineConfiguration>,

В противном случае странно, что вы пишете, вы устанавливаете camunda.war к ванильному коту, но оставьте ссылку на ваш bpm-platform.xml файл, который вообще не используется, когда вы не используете подход с общим процессором.