topic Re: concurrency in taskService.claim() in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/concurrency-in-taskservice-claim/m-p/66960#M42646 <HTML><HEAD></HEAD><BODY><SPAN>Yes, you are right. An ActivitiOptimisticLockException will be thrown and transaction will be rolled back for the one that came too late <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 /><SPAN>We're using a version-field on all entities and check is performed when updates are flushed.</SPAN></BODY></HTML> Tue, 14 Jun 2011 14:17:43 GMT frederikherema1 2011-06-14T14:17:43Z concurrency in taskService.claim() https://connect.hyland.com/t5/alfresco-archive/concurrency-in-taskservice-claim/m-p/66959#M42645 Hi,Looking at the code, am i right in assuming that a task currently can be claimed by 2 users (or threads or whatever) at the same time without throwing an exception ? The last one to update the database would win, but maybe there is an ibatis mechanism in place (optimistic locking) to prevent this Tue, 14 Jun 2011 14:06:44 GMT https://connect.hyland.com/t5/alfresco-archive/concurrency-in-taskservice-claim/m-p/66959#M42645 heymjo 2011-06-14T14:06:44Z Re: concurrency in taskService.claim() https://connect.hyland.com/t5/alfresco-archive/concurrency-in-taskservice-claim/m-p/66960#M42646 <HTML><HEAD></HEAD><BODY><SPAN>Yes, you are right. An ActivitiOptimisticLockException will be thrown and transaction will be rolled back for the one that came too late <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 /><SPAN>We're using a version-field on all entities and check is performed when updates are flushed.</SPAN></BODY></HTML> Tue, 14 Jun 2011 14:17:43 GMT https://connect.hyland.com/t5/alfresco-archive/concurrency-in-taskservice-claim/m-p/66960#M42646 frederikherema1 2011-06-14T14:17:43Z