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.

JavaDelegate - New instance per call?

kaech

Are the JavaDelegates and ActivityBehaviors reused or is a new instance created for each call?
It might happen that they are called from different job executor threads. Are they thread safe?
Is there anything to keep in mind especially when working with ActivityExecution inside of ann Activity Behavior?

Thank you in advance

Find more posts tagged with

Comments

roig

AFAIK these delegate classes are not thread safe. They are instantiated only once, and then used with no thread safe mechanism (this is up to the class implementation)

meyerd

Hi roig

JavaDelegate and ActivityBehavior instances are static by design. They are not threadsafe.

C.f: user manual: http://activiti.org/userguide/index.html#bpmnJavaServiceTask

Note: there will be only one instance of that Java class created for the serviceTask it is defined on. All process-instances share the same class instance that will be used to call execute(DelegateExecution). This means that the class must not use any member variables and must be thread-safe, since it can be executed simultaneously from different threads. This also influences the way Field injection is handled.