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.

How to avoid multiple calls with the same processInstanceId

rufini

Hi

I would like to know if Activiti can help me to block a second call with the same processInstanceId while a serviceTask is running.

Scenario: a web user retrying with the same processInstanceId while processing the previous request. (I've no control over UI)

Can Activiti help me to fix this, or should I do it manually?

Thanks!

Find more posts tagged with

Comments

heymjo

'blocking a second call' can mean just about anything, but IMO process concurrency (or restrictions thereof) should be modelled outside of the business process.

If you really must model it inside the process then you might be able to use an executionlistener on the start event of the process, and throw an exception or something when you detect that another instance of the same process is running.

frederikherema1

Activiti has optimistic locking in place. In case two threads concurrently eg. complete the same task on a process-instance, one of them will get a "org.activiti.engine.ActivitiOptimisticLockingException". Your logic, consuming the Activiti API, can catch this and handle accordingly.