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.

Concurrency exception on timer event

tstephen

Hi,

I have found that the time taken to start a process instance can be too long for my purposes when the process definition includes relatively slow (hundreds of milliseconds) activities immediately after the start event.

In order to force Activiti to return immediately after starting the process I have put a timer event as the first task with a very short (1 second) timeout. In unit tests this achieves my goal of a faster process start but in the tomcat environment I am seeing the following stack trace.

I have two questions:
1. is there a better way to ensure the fastest possible process start? It seems like it would be good to have an Activiti flag to persist the process for async handling, does such a thing exist?
2. Any ideas how to avoid the Job thread hitting this concurrency exception? I'd prefer to avoid simply trying longer delays in the timer event until it works

Thanks, Tim

SEVERE: Error while closing command context
org.activiti.engine.ActivitiOptimisticLockingException: TimerEntity[62760] was updated by another transaction concurrently
&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.db.DbSqlSession.flushUpdates(DbSqlSession.java:425)
&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.db.DbSqlSession.flush(DbSqlSession.java:338)
&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.interceptor.CommandContext.flushSessions(CommandContext.java:147)
&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.interceptor.CommandContext.close(CommandContext.java:103)
&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:49)
&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:33)
&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.jobexecutor.JobAcquisitionThread.run(JobAcquisitionThread.java:63)‍‍‍‍‍‍‍‍‍

Find more posts tagged with

Comments

ronald_van_kuij

It seems like it would be good to have an Activiti flag to persist the process for async handling, does such a thing exist?

http://tinyurl.com/43v2uvo