topic Re: JobExecutor deadlocks on MSSQL in Alfresco Archive

JobExecutor deadlocks on MSSQL

andreasa — Fri, 28 Jun 2013 12:04:49 GMT

Windows platform, Tomcat 7, MSSQL 2008/2012, Activiti 5.12On our production system we cannot start our application when there are several (~10+) jobs in ACT_RU_JOB that has a DUEDATE_ that has passed. The application/activiti starts puts a lock on 15 rows, starts polling the jobs and then stalls aft

Re: JobExecutor deadlocks on MSSQL

andreasa — Fri, 28 Jun 2013 12:52:53 GMT

Inspired by this: http://forums.activiti.org/content/activiti-thread-safety

I tried setting connection pool to max 1, min 1. This resulted in the application hanging exactly like in the production-environment.

I guess it could be the connection pool, although I'm already using C3P0 and not DBCP.

I can then also semi conclude that the database in the production system only has one or very few connections awailable, since I get the same behaviour when only giving the connection pool 1 connection.

Re: JobExecutor deadlocks on MSSQL

andreasa — Mon, 01 Jul 2013 07:48:34 GMT

This can be solved by creating the indexes that long suggests in this thread: http://forums.activiti.org/content/deadlock-load-test-db2

Before MSSQL would throw deadlocks on as little as 15 jobs with a passed duedate and with these indexes I can run 3000 jobs with no problem (other than a primary key violation on the activity table, but thats a different story).

Re: JobExecutor deadlocks on MSSQL

andreasa — Mon, 01 Jul 2013 08:26:46 GMT

It is also suggested in http://forums.activiti.org/content/deadlock-mssql-2008-while-loadtesting that upgrading to 5.13 might resolve this. Haven't got time to test that right now though.