topic Re: Activiti deadlock occurs under JMeter performance test in Alfresco Archive

Activiti deadlock occurs under JMeter performance test

lepike — Tue, 12 Jul 2011 10:19:02 GMT

Hi Guys!One of my project uses Activiti Workflow Engine. The usage of the engine is very comfortable and I'm very satisfied with it, but I have a little problem with concurrency. We have a wicket spring application with embedded activiti workflow engine. It works fine without concurrent users, but d

Re: Activiti deadlock occurs under JMeter performance test

ronald_van_kuij — Tue, 12 Jul 2011 10:31:34 GMT

Creating indexes on relevant columns (for specifict queries you use) is the first thing to do. This prevents full table scans. Activiti comes with a basic set of indexes and with all the enhancements in the queries this can result in deadlocks

Re: Activiti deadlock occurs under JMeter performance test

lepike — Tue, 12 Jul 2011 11:17:54 GMT

Thx for your help! I will check the activiti queries and the indexes on the tables. Hope it will help with deadlocks. MSSQL database can be a problem? Does it supported well by Activiti?

Best regards,
Levi

Re: Activiti deadlock occurs under JMeter performance test

lepike — Tue, 12 Jul 2011 12:56:55 GMT

I have made some indexes on activiti tables. Now I have only one deadlock. It comes from the selectTaskByQueryCriteriaSql Ibatis sql. I cannot index the tables to make this complex sql to work without deadlock. Have you got any idea?

Thx!

Levi

Re: Activiti deadlock occurs under JMeter performance test

heymjo — Thu, 14 Jul 2011 08:36:33 GMT

Does Activiti set the readonly flag on each connection where it only selects data ? That could help avoid this type of errors as well IIRC.

Re: Activiti deadlock occurs under JMeter performance test

ronald_van_kuij — Thu, 14 Jul 2011 12:48:52 GMT

That could help to yes. I have no idea if Activiti has these kinds of things… there are ibatis config files with everything in it. So if you have suggestions/can try things, feel free

Re: Activiti deadlock occurs under JMeter performance test

lepike — Mon, 18 Jul 2011 14:47:04 GMT

Thanks for the help. The problem still valid. I have no idea to solve…

Re: Activiti deadlock occurs under JMeter performance test

mahavirj — Mon, 18 Jul 2011 20:51:50 GMT

do you mind sharing the indices you created? also, spring has some transaction settings like propagation_required or propagation_supports that could be tinkered with. what driver are you using for sqlserver?

Re: Activiti deadlock occurs under JMeter performance test

lepike — Tue, 19 Jul 2011 20:12:10 GMT

JTDS 1.2.4 and the Microsoft JDBC driver were tested also.
The transaction management is the following:
on workflow service class: propagation=supports, readonly=true
on every crud method in this service class: propagation=required, readonly=false

So the startProcess function, every service task function and human task function has propagation=required, readonly=false settings, because they are crud methods in my application.

Is this a bad usage?
Thanks for the help.

Levi

Re: Activiti deadlock occurs under JMeter performance test

mahavirj — Wed, 20 Jul 2011 15:02:18 GMT

looks ok….i use websphere and the article below was useful for txn settings using spring/hibernate. perhaps some of this may be of relevant to your scenario

http://www.ibm.com/developerworks/websphere/techjournal/0609_alcott/0609_alcott.html?ca=drs-

Re: Activiti deadlock occurs under JMeter performance test

notizklotz — Tue, 27 Dec 2011 17:09:34 GMT

I've got similar problems on MS SQL 2008. I was able to resolve some deadlock situations by enabling READ_COMMITTED_SNAPSHOT which is an alternative implementation of the READ COMMITED level which is closer to how Oracle and MySQL implement it.
http://msdn.microsoft.com/en-us/library/ee384251%28v=sql.100%29.aspx
http://msdn.microsoft.com/en-us/library/ms177404.aspx

However, I still got deadlocks when multiple users are sending signals in different process instances.

@lepike
Could you please share the index optimizations you did?

Re: Activiti deadlock occurs under JMeter performance test

ronald_van_kuij — Tue, 27 Dec 2011 17:24:49 GMT

Besides the ideces, one important 'improvement' could be using the 'other' id generator:

http://jira.codehaus.org/browse/ACT-789

Re: Activiti deadlock occurs under JMeter performance test

flavio_donze — Tue, 09 Apr 2013 11:12:25 GMT

Just for the record, the answer here "solved" the dead lock problems:
http://stackoverflow.com/questions/6662504/activiti-deadlock-occurs-under-jmeter-performance-test
"I removed all of the timers from my activiti diagram and deadlocks are disappeared. I don't know why, but it works."

Re: Activiti deadlock occurs under JMeter performance test

ronald_van_kuij — Wed, 10 Apr 2013 07:59:17 GMT

Why is removing all the timers a solution? I don't get that. Aounds like havily modifying your process.

Re: Activiti deadlock occurs under JMeter performance test

flavio_donze — Wed, 10 Apr 2013 09:09:51 GMT

Hello Ronald

Your right it is not a solution, just wanted to make clear that it solved the transaction problem.

In my case I just had to remove one.

greets
Flavio

Re: Activiti deadlock occurs under JMeter performance test

trond_nordli — Mon, 01 Jul 2013 07:01: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: Activiti deadlock occurs under JMeter performance test

frederikherema1 — Wed, 03 Jul 2013 09:48:14 GMT

There were some indexed added to FK-columns to prevent full-table locking of FK-referenced entities. However, not sure this has made the 5.13-realease (for mssql)… Anyway, glad the issue is sorted now