topic Dead locks - jmeter testing with concurrent users in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/dead-locks-jmeter-testing-with-concurrent-users/m-p/156091#M110358 <HTML><HEAD></HEAD><BODY><SPAN>Hi,</SPAN><BR /><BR /><SPAN>We are using Ms sql server as database.&nbsp; When running the process with jmeter its throwing the below error.&nbsp;&nbsp; Not sure what the real issue here is.&nbsp; </SPAN><BR /><BR /><SPAN>I have read other posts that this kind of problem is resolved in 5.13 but we are on 5.10.&nbsp; Is there a patch that we could use?</SPAN><BR /><BR /><SPAN>- Database read committed snapshot is on</SPAN><BR /><SPAN>- single thread works fine.&nbsp; 3 users concurrency has problems</SPAN><BR /><SPAN>- Dont have any timers in my process but have wait task signals.</SPAN><BR /><BR /><SPAN>IS it something to do with my transaction propagation settings?&nbsp; I am using spring's default propagation settings.</SPAN><BR /><BR /><SPAN>Thanks,</SPAN><BR /><SPAN>Raj</SPAN><BR /><SPAN>——–Error——-</SPAN><BR /><SPAN>&lt;blockcode&gt;</SPAN><BR /><SPAN>### Error updating database.&nbsp; Cause: com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 70) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.</SPAN><BR /><SPAN>### The error may involve org.activiti.engine.impl.persistence.entity.TaskEntity.insertTask-Inline</SPAN><BR /><SPAN>### The error occurred while setting parameters</SPAN><BR /><SPAN>### SQL: insert into ACT_RU_TASK (ID_, REV_, NAME_, PARENT_TASK_ID_, DESCRIPTION_, PRIORITY_, CREATE_TIME_, OWNER_,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ASSIGNEE_, DELEGATION_, EXECUTION_ID_, PROC_INST_ID_, PROC_DEF_ID_, TASK_DEF_KEY_, DUE_DATE_)&nbsp;&nbsp;&nbsp;&nbsp; values (?,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; )</SPAN><BR /><SPAN>### Cause: com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 70) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.apache.ibatis.exceptions.ExceptionFactory.wrapException(ExceptionFactory.java:23)</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.java:147)</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.apache.ibatis.session.defaults.DefaultSqlSession.insert(DefaultSqlSession.java:134)</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.db.DbSqlSession.flushInserts(DbSqlSession.java:459)</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.db.DbSqlSession.flush(DbSqlSession.java:369)</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.interceptor.CommandContext.flushSessions(CommandContext.java:157)</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.interceptor.CommandContext.close(CommandContext.java:109)</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:49)</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.activiti.spring.SpringTransactionInterceptor$1.doInTransaction(SpringTransactionInterceptor.java:42)</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:130)</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.activiti.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:40)</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:33)</SPAN><BR /><SPAN>&nbsp;&nbsp;&nbsp;at org.activiti.engine.impl.RuntimeServiceImpl.signal(RuntimeServiceImpl.java:141)</SPAN><BR /><SPAN>&lt;/blockcode&gt;&nbsp;&nbsp;&nbsp;</SPAN></BODY></HTML> Wed, 02 Oct 2013 10:04:50 GMT kethur 2013-10-02T10:04:50Z Dead locks - jmeter testing with concurrent users https://connect.hyland.com/t5/alfresco-archive/dead-locks-jmeter-testing-with-concurrent-users/m-p/156091#M110358 Hi,We are using Ms sql server as database.&nbsp; When running the process with jmeter its throwing the below error.&nbsp;&nbsp; Not sure what the real issue here is.&nbsp; I have read other posts that this kind of problem is resolved in 5.13 but we are on 5.10.&nbsp; Is there a patch that we could use?- Database read commit Wed, 02 Oct 2013 10:04:50 GMT https://connect.hyland.com/t5/alfresco-archive/dead-locks-jmeter-testing-with-concurrent-users/m-p/156091#M110358 kethur 2013-10-02T10:04:50Z Re: Dead locks - jmeter testing with concurrent users https://connect.hyland.com/t5/alfresco-archive/dead-locks-jmeter-testing-with-concurrent-users/m-p/156092#M110359 <HTML><HEAD></HEAD><BODY><SPAN>We added some indexes on foreign keys. If these indexes are not present, full-table lock is done on the referenced table when an entity in the parent-table is updated, which causes the deadlocks.</SPAN><BR /><BR /><SPAN>See </SPAN><A href="https://github.com/Activiti/Activiti/commit/22f6c8d0cf126320addb90f86495e89e7d656939" rel="nofollow noopener noreferrer">https://github.com/Activiti/Activiti/commit/22f6c8d0cf126320addb90f86495e89e7d656939</A><SPAN> for the involved indexes you can add (double-check if all tables used are present in 5.10)</SPAN></BODY></HTML> Wed, 02 Oct 2013 10:29:56 GMT https://connect.hyland.com/t5/alfresco-archive/dead-locks-jmeter-testing-with-concurrent-users/m-p/156092#M110359 frederikherema1 2013-10-02T10:29:56Z Re: Dead locks - jmeter testing with concurrent users https://connect.hyland.com/t5/alfresco-archive/dead-locks-jmeter-testing-with-concurrent-users/m-p/156093#M110360 <HTML><HEAD></HEAD><BODY><SPAN>Hi,</SPAN><BR /><BR /><SPAN>This is resolved by creating 5.13 indexes in 5.10.&nbsp; Now, the deadlock is disappeared and works fine.</SPAN><BR /><BR /><SPAN>Many thanks for your help.</SPAN><BR /><SPAN>Raj</SPAN></BODY></HTML> Thu, 03 Oct 2013 11:55:37 GMT https://connect.hyland.com/t5/alfresco-archive/dead-locks-jmeter-testing-with-concurrent-users/m-p/156093#M110360 kethur 2013-10-03T11:55:37Z