topic Re: Deadlock on MSSQL 2008 while loadtesting in Alfresco Archive

Deadlock on MSSQL 2008 while loadtesting

sazzadul — Thu, 12 Jan 2012 14:31:53 GMT

Hei,I am getting the following exception while running loadtest. Is there any twik in the configuration I can do to avoid this exception ?I havn't created any db indexes other than what was already added by activity engine.I am having this problem each time I run a loadtest. Is this specific to mssq

Re: Deadlock on MSSQL 2008 while loadtesting

meyerd — Thu, 12 Jan 2012 14:47:01 GMT

Hello sazzadul,

Without having looked into you stacktraces in detail:
are you using org.activiti.engine.impl.persistence.StrongUuidGenerator (See ACT-789) ?

Re: Deadlock on MSSQL 2008 while loadtesting

sazzadul — Thu, 12 Jan 2012 15:17:31 GMT

Hello sazzadul,

Without having looked into you stacktraces in detail:
are you using org.activiti.engine.impl.persistence.StrongUuidGenerator (See ACT-789) ?

No I am not, will this solve the problem ?

I have tried with this settings without any luck


 <tx:advice id="txAdvice" transaction-manager="transactionManager">
    <tx:attributes>
       <tx:method name="get*" propagation="REQUIRED" read-only="true" />
       <tx:method name="set*" propagation="REQUIRES_NEW" />
       <tx:method name="*" />
    </tx:attributes>
 </tx:advice>

Re: Deadlock on MSSQL 2008 while loadtesting

sazzadul — Thu, 12 Jan 2012 21:58:27 GMT

Hello sazzadul,

Without having looked into you stacktraces in detail:
are you using org.activiti.engine.impl.persistence.StrongUuidGenerator (See ACT-789) ?

I have now tried StrongUuidGenerator as well and result is same also the deadlock still occurs.

Do you have other suggestions ?

Re: Deadlock on MSSQL 2008 while loadtesting

notizklotz — Fri, 13 Jan 2012 15:31:10 GMT

You are not alone…

Please see http://forums.activiti.org/en/viewtopic.php?f=6&t=2029 which is also a topic in this forum about this problem. For using MS SQL's READ_COMMITTED_SNAPSHOT setting resolved most deadlocks, but not all. See the other topic for how to enable that and why that resolves deadlocks.

Re: Deadlock on MSSQL 2008 while loadtesting

trond_nordli — Mon, 01 Jul 2013 06:58:14 GMT

We had a similar problem on MS SQL 2008 (SP3) but this problem seems to have disappeared after we upgraded the project from Activiti version 5.12.1 to Activiti version 5.13.

We have also tested this out successfully in Activi Benchmark project, where Activiti version 5.13 works but the older version does not work (dead locks problem) on MS SQL 2008.

Activiti Benchmark project:
http://www.jorambarrez.be/blog/2012/06/28/the-activiti-performance-showdown/

Re: Deadlock on MSSQL 2008 while loadtesting

jbarrez — Mon, 01 Jul 2013 09:00:06 GMT

Yes. We had a customer seeing a similar issue on MSSQL and fixed it in 5.13.

Re: Deadlock on MSSQL 2008 while loadtesting

asite — Mon, 28 Mar 2016 08:27:09 GMT

Hi jbarrez,
I am using 'org.activiti:activiti-spring:5.15.1' version and I have been facing the same problem of deadlock for mssql server from last one month and still I hadn't find any solution.

I had tried below solution
1. Created Missing index on activiti's table
2. Used BoneCP instead of DBCP

but still produce deadlock when performing taskService.complete() command in high concurrency.

Any help….

Re: Deadlock on MSSQL 2008 while loadtesting

jbarrez — Mon, 04 Apr 2016 10:20:49 GMT

Any reason why using such an old version?
If I remember correctly, the problem with mssql back in the day was mising indices … maybe that's worth to look into?