nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Problem in Activiti Camel Task

amey_vaidya

Hi..

We have a workflow with many camel tasks (to avoid Optimistic Locking Exception). When we run more than one instance of that bpmn(say 100), we are observing that sometimes one or more process instance remains incomplete. While inspecting database 'act_ru_execution' we found camel receive tasks for the incomplete process-instances there.

Why it is happening?

Find more posts tagged with

Comments

trademak

That's difficult to say without additional context. But it could be that sometimes the receive task is initiated after Camel already tried to sent the response message back to the Activiti Engine.
BTW, we added support for asynchronous parallel gateways which should also solve the optimistic lock exception without the need for Camel. We plan to do a 5.15.2 release shortly that includes this new functionality.

Best regards,

amey_vaidya

hi trademark

It will be great if the next release is coming up with asynch integration. Can you tell me approximate date of 5.15.2 release. Can we expect it to be released in a month ?
We also have a requirement for Sybase database support. Is there any plan to support Sybase in next release of Activiti ?

Thanks

Thanks