TimerEntity[XXXXXX] was updated by another transaction concurrently

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.

swamy2156

Hi,

I wrote  a process with timer boundary event & a service task. For every 2 minutes serviceTask will be called and send some notifications(linux box#1 where jobExecutorActivate = true)
I wrote a service to complete the human task( linux box#2 - where jobExecutorActivate = false). Occassionally while updating the task using the service which I written I am getting this error
                            "TimerEntity[XXXXXXX] was updated by another transaction concurrently"
in perticular scenarios where updating the task and timer event executed simultaniously.

box#1 processEngine configuration is as follows.

  <bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration">
    <property name="dataSource" ref="dataSource" />
    <property name="transactionManager" ref="transactionManager" />
    <property name="history" value="full" />
    <property name="databaseSchemaUpdate" value="false" />
    <property name="jobExecutorActivate" value="true" />
    <property name="jobExecutor">
      <bean class="org.activiti.engine.impl.jobexecutor.DefaultJobExecutor">
        <property name="corePoolSize" value="1"/>
        <property name="maxPoolSize" value="1"/>
      </bean>
    </property>
    <property name="jdbcPingEnabled" value="true" />
    <property name="jdbcPingQuery" value="select 1" />
    <property name="processDefinitionCacheLimit" value="20" />
    <property name="processEngineName" value="default"></property>
    <property name="customSessionFactories">
      <list>
        <bean class="com.uprr.bpm.rest.services.ldap.LDAPUserManagerFactory">
          <constructor-arg ref="ldapConnectionParams" />
        </bean>
        <bean class="com.uprr.bpm.rest.services.ldap.LDAPGroupManagerFactory">
          <constructor-arg ref="ldapConnectionParams" />
        </bean>
      </list>
    </property>
  </bean>
  <bean id="transactionManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
    <property name="dataSource" ref="dataSource" />
  </bean>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Any help will be really appreciated.

Thanks,
Swamy.

frederikherema1

That's perfectly normal, that exception. It means the optimistic locking stategy works, as the transaction the "job execution" was in will not be committed due to the fact that the user-task is completed and the timer doesn't exist anymore (that's what I'm guessing).

Its a specific Activiti exception-type (ActivitiOptimisticLockException) and can occur in situations you're describing (simultaneous modification of timer state). The transaction that is first, wins. The other is rolled back…