topic Re: Race condition in job executor? in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/race-condition-in-job-executor/m-p/123850#M87168 <HTML><HEAD></HEAD><BODY><SPAN>When a job is locked for XX seconds and not unlocked, the job-executor assumes something went terribly wrong while executing. THis has noting to do with transaction-timeout or millisToWait (as this is the poll-interval for acquiring jobs ready to execute).</SPAN><BR /><BR /><SPAN>See the setting for lockTimeInMillis (protected int lockTimeInMillis = 5 * 60 * 1000<img id="smileywink" class="emoticon emoticon-smileywink" src="https://connect.hyland.com/i/smilies/16x16_smiley-wink.png" alt="Smiley Wink" title="Smiley Wink" /> which defaults to 5 minutes. So if the first thread in the pool acquired the job and is executing it (lock-time is set) for longer than 5 minutes, the job-executor will use another thread to execute the job, effectively setting the lock-time etc. again.</SPAN><BR /><BR /><SPAN>This results in the first thread, when it returns, to get an ActivitiConcurrentModificationException when the transaction is committed, rolling back the first job-execution. That's the way it's supposed to work. You should make sure the lockTimeInMillis is larger than the transaction-timeout to ensure the job being "marked as executed/failed" due to transaction-timeout before it's considered as "stuck"…</SPAN></BODY></HTML> Wed, 17 Jul 2013 10:53:31 GMT frederikherema1 2013-07-17T10:53:31Z Race condition in job executor? https://connect.hyland.com/t5/alfresco-archive/race-condition-in-job-executor/m-p/123849#M87167 Hello all,We had the following case, an async and exclusive service task calling a cdi method. The job executor is configured to lock jobs for 5 mins so as the jboss server transaction timeout. It has been noticed that this cdi method, under heavy load, had its transaction timed out so nothing was u Mon, 15 Jul 2013 19:36:17 GMT https://connect.hyland.com/t5/alfresco-archive/race-condition-in-job-executor/m-p/123849#M87167 mandas 2013-07-15T19:36:17Z Re: Race condition in job executor? https://connect.hyland.com/t5/alfresco-archive/race-condition-in-job-executor/m-p/123850#M87168 <HTML><HEAD></HEAD><BODY><SPAN>When a job is locked for XX seconds and not unlocked, the job-executor assumes something went terribly wrong while executing. THis has noting to do with transaction-timeout or millisToWait (as this is the poll-interval for acquiring jobs ready to execute).</SPAN><BR /><BR /><SPAN>See the setting for lockTimeInMillis (protected int lockTimeInMillis = 5 * 60 * 1000<img id="smileywink" class="emoticon emoticon-smileywink" src="https://connect.hyland.com/i/smilies/16x16_smiley-wink.png" alt="Smiley Wink" title="Smiley Wink" /> which defaults to 5 minutes. So if the first thread in the pool acquired the job and is executing it (lock-time is set) for longer than 5 minutes, the job-executor will use another thread to execute the job, effectively setting the lock-time etc. again.</SPAN><BR /><BR /><SPAN>This results in the first thread, when it returns, to get an ActivitiConcurrentModificationException when the transaction is committed, rolling back the first job-execution. That's the way it's supposed to work. You should make sure the lockTimeInMillis is larger than the transaction-timeout to ensure the job being "marked as executed/failed" due to transaction-timeout before it's considered as "stuck"…</SPAN></BODY></HTML> Wed, 17 Jul 2013 10:53:31 GMT https://connect.hyland.com/t5/alfresco-archive/race-condition-in-job-executor/m-p/123850#M87168 frederikherema1 2013-07-17T10:53:31Z