topic Concurrency exception on timer event in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/concurrency-exception-on-timer-event/m-p/66863#M42578 <HTML><HEAD></HEAD><BODY><SPAN>Hi,</SPAN><BR /><BR /><SPAN>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. </SPAN><BR /><BR /><SPAN>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. </SPAN><BR /><BR /><SPAN>I have two questions: </SPAN><BR /><SPAN>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? </SPAN><BR /><SPAN>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&nbsp; <img id="smileywink" class="emoticon emoticon-smileywink" src="https://connect.hyland.com/i/smilies/16x16_smiley-wink.png" alt="Smiley Wink" title="Smiley Wink" /> </SPAN><BR /><BR /><SPAN>Thanks, Tim</SPAN><BR /><PRE class="language-none line-numbers"><CODE>SEVERE: Error while closing command context<BR />org.activiti.engine.ActivitiOptimisticLockingException: TimerEntity[62760] was updated by another transaction concurrently<BR />&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.db.DbSqlSession.flushUpdates(DbSqlSession.java:425)<BR />&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.db.DbSqlSession.flush(DbSqlSession.java:338)<BR />&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.interceptor.CommandContext.flushSessions(CommandContext.java:147)<BR />&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.interceptor.CommandContext.close(CommandContext.java:103)<BR />&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:49)<BR />&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:33)<BR />&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.jobexecutor.JobAcquisitionThread.run(JobAcquisitionThread.java:63)<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE></BODY></HTML> Mon, 22 Aug 2011 13:58:26 GMT tstephen 2011-08-22T13:58:26Z Concurrency exception on timer event https://connect.hyland.com/t5/alfresco-archive/concurrency-exception-on-timer-event/m-p/66863#M42578 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 Mon, 22 Aug 2011 13:58:26 GMT https://connect.hyland.com/t5/alfresco-archive/concurrency-exception-on-timer-event/m-p/66863#M42578 tstephen 2011-08-22T13:58:26Z Re: Concurrency exception on timer event https://connect.hyland.com/t5/alfresco-archive/concurrency-exception-on-timer-event/m-p/66864#M42579 <HTML><HEAD></HEAD><BODY><BLOCKQUOTE class="jive-quote">It seems like it would be good to have an Activiti flag to persist the process for async handling, does such a thing exist?</BLOCKQUOTE><BR /><A href="http://tinyurl.com/43v2uvo" rel="nofollow noopener noreferrer">http://tinyurl.com/43v2uvo</A></BODY></HTML> Mon, 22 Aug 2011 15:05:42 GMT https://connect.hyland.com/t5/alfresco-archive/concurrency-exception-on-timer-event/m-p/66864#M42579 ronald_van_kuij 2011-08-22T15:05:42Z