topic Re: Deadlock in cluster during AcquireJobsCmd in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/deadlock-in-cluster-during-acquirejobscmd/m-p/158338#M112451 <HTML><HEAD></HEAD><BODY><SPAN>Thanks for posting this. We had a team call on it and found out that you indeed found a bug in the job executor.</SPAN><BR /><BR /><SPAN>The corresponding Jira issue is </SPAN><A href="http://jira.codehaus.org/browse/ACT-1879#comment-337677" rel="nofollow noopener noreferrer">http://jira.codehaus.org/browse/ACT-1879#comment-337677</A><BR /><SPAN>It's fixed at </SPAN><A href="https://github.com/Activiti/Activiti/commit/1ea692de8bd2626fd2836ed31d160a036c3f4aa8" rel="nofollow noopener noreferrer">https://github.com/Activiti/Activiti/commit/1ea692de8bd2626fd2836ed31d160a036c3f4aa8</A><BR /><BR /><SPAN>This will be part of the next release. However, you can apply the same simple fix as in the git commit (set the maxJobsPerAcquisition to one).</SPAN><BR /><BR /><SPAN>Thank you very much!</SPAN></BODY></HTML> Thu, 19 Dec 2013 10:32:14 GMT jbarrez 2013-12-19T10:32:14Z Deadlock in cluster during AcquireJobsCmd https://connect.hyland.com/t5/alfresco-archive/deadlock-in-cluster-during-acquirejobscmd/m-p/158337#M112450 I have a cluster of 2 Activiti 5.14 instances, sharing the same PostgreSQL 9.1 database. I have a process with timers.From time to time I experience a deadlock during AcquireJobsCmd execution:2013-12-17 12:00:01,083 Thread-96&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ERROR [&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; impl.interceptor.CommandContext] [&nbsp;&nbsp;&nbsp; Wed, 18 Dec 2013 14:31:26 GMT https://connect.hyland.com/t5/alfresco-archive/deadlock-in-cluster-during-acquirejobscmd/m-p/158337#M112450 tomasz_lewandow 2013-12-18T14:31:26Z Re: Deadlock in cluster during AcquireJobsCmd https://connect.hyland.com/t5/alfresco-archive/deadlock-in-cluster-during-acquirejobscmd/m-p/158338#M112451 <HTML><HEAD></HEAD><BODY><SPAN>Thanks for posting this. We had a team call on it and found out that you indeed found a bug in the job executor.</SPAN><BR /><BR /><SPAN>The corresponding Jira issue is </SPAN><A href="http://jira.codehaus.org/browse/ACT-1879#comment-337677" rel="nofollow noopener noreferrer">http://jira.codehaus.org/browse/ACT-1879#comment-337677</A><BR /><SPAN>It's fixed at </SPAN><A href="https://github.com/Activiti/Activiti/commit/1ea692de8bd2626fd2836ed31d160a036c3f4aa8" rel="nofollow noopener noreferrer">https://github.com/Activiti/Activiti/commit/1ea692de8bd2626fd2836ed31d160a036c3f4aa8</A><BR /><BR /><SPAN>This will be part of the next release. However, you can apply the same simple fix as in the git commit (set the maxJobsPerAcquisition to one).</SPAN><BR /><BR /><SPAN>Thank you very much!</SPAN></BODY></HTML> Thu, 19 Dec 2013 10:32:14 GMT https://connect.hyland.com/t5/alfresco-archive/deadlock-in-cluster-during-acquirejobscmd/m-p/158338#M112451 jbarrez 2013-12-19T10:32:14Z