topic Re: Does Activiti need new db connection for each separate workflow? in Alfresco Archive

Does Activiti need new db connection for each separate workflow?

alper — Fri, 05 Dec 2014 08:29:38 GMT

Hi,First of all, I found Activiti pretty impressive in part of performance when I became more or less educated in the workflow technology and BPMN. Thanks for that.But there is a thing that I didn't find workaround for without giving up the performance.In my tests I see that if I launch new separate

Re: Does Activiti need new db connection for each separate workflow?

trademak — Fri, 05 Dec 2014 12:27:41 GMT

There's no magical solution for this problem. Connection pooling is definitely the area to focus on. Also, you could try to keep the transaction to start a new process instance as short as possible. This would be possible to using asynchronous tasks for example.

Best regards,

Re: Does Activiti need new db connection for each separate workflow?

alper — Fri, 05 Dec 2014 12:52:51 GMT

As it is impossible to make the whole process asynchronous from the start, I make the first activity asynchronous to transfer the whole process to the asynchronous mode as soon as possible.
Is that what you mean?

Also, maybe you can give me a piece of advice how to tune the connection timeout in the Activiti Engine to make the pool's queue useful in this situation? Though it is definitely a half-measure…

Re: Does Activiti need new db connection for each separate workflow?

trademak — Fri, 05 Dec 2014 13:07:53 GMT

Yes that's what I mean indeed.
I don't think the connection timeout needs special tweaking for Activiti.

Best regards,