topic Re: activiti cluster db deadlocks in Alfresco Archive

activiti cluster db deadlocks

oliverkaint — Sat, 03 Mar 2012 19:21:19 GMT

Are the clustering capabilities supported in Activiti 5.6?. We have deployed our application in different machines, testing db deadlocks appear within processes when running stress test. However if we stop one of the machines deadlocks problems disappear. How do to configure activiti for clustering?

Re: activiti cluster db deadlocks

trademak — Mon, 05 Mar 2012 19:15:35 GMT

Hi,

What kind of stack traces do you get? Did you also try the same testing with Activiti 5.9?
Activiti should just work fine when deployed on multiple machines.

Best regards,

Re: activiti cluster db deadlocks

meyerd — Wed, 07 Mar 2012 20:16:21 GMT

Consider using the org.activiti.engine.impl.persistence.StrongUuidGenerator iststead of the DbIdGenerator. The DbIdGenerator is known to produce deadlocks.

Re: activiti cluster db deadlocks

meyerd — Wed, 07 Mar 2012 20:17:12 GMT

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

Re: activiti cluster db deadlocks

heymjo — Thu, 08 Mar 2012 07:16:06 GMT

Consider using the org.activiti.engine.impl.persistence.StrongUuidGenerator iststead of the DbIdGenerator. The DbIdGenerator is known to produce deadlocks.

Is there a particular reason why this StrongUuidGenerate has not been made the default then ? It was marked EXPERIMENTAL already in 5.8 iirc.

Re: activiti cluster db deadlocks

bernd_ruecker — Thu, 08 Mar 2012 07:48:14 GMT

Basically because people don't like the non-readable UUID's, that's why the other one is still default.

Re: activiti cluster db deadlocks

smirzai — Fri, 02 Nov 2012 14:08:04 GMT

Hi oliverkaint
I am interested to know if you have tested the clustering of Activiti. Has there been any practical deployment of activiti in embedded mode in a cluster ?

– Saeid