activiti cluster db deadlocks

[oliverkaint]

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?.

regards

[trademak]

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,

[meyerd]

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

[meyerd]

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

[heymjo]

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.

[bernd_ruecker]

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

[smirzai]

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