topic Re: When startProcessInstanceByKey gives the instance back ? in Alfresco Archive

When startProcessInstanceByKey gives the instance back ?

vire7777 — Wed, 05 Dec 2012 10:46:16 GMT

Hi all A little question but SO important for me.I ve created a workflow instance launcher with the code rocessInstance instance = runtimeService.startProcessInstanceByKey(processKey);‍But something strange about that !In my workflow, i have two javaservicetask then a human task and i ve seen th

Re: When startProcessInstanceByKey gives the instance back ?

sothach — Wed, 05 Dec 2012 14:10:55 GMT

But could i do something for having it directly after the instance launch because i need it before the instance reaches the first javaservice task.

If you make set the first task as async=true, then startProcessInstanceByKey will return immediately (the workflow is now running in a new thread)

Re: When startProcessInstanceByKey gives the instance back ?

ronald_van_kuij — Wed, 05 Dec 2012 15:00:59 GMT

Maybe this should be mentioned very early in the docs…

Re: When startProcessInstanceByKey gives the instance back ?

vire7777 — Thu, 06 Dec 2012 09:59:37 GMT

But if i want to use "async=true", i don t know why, the workflow don't find my class anymore…

Re: When startProcessInstanceByKey gives the instance back ?

dognose — Thu, 06 Dec 2012 10:15:12 GMT

which class?

Re: When startProcessInstanceByKey gives the instance back ?

vire7777 — Thu, 06 Dec 2012 10:38:10 GMT

My javaservicetask calls a class "com.test.ActivitiTask"
When i do not set async, then it calls my Execute method on this class "com.test.ActivitiTask"
If i put "async = true" then it doesn t find my class "com.test.ActivitiTask" and doesn t lauch my method execute…

Re: When startProcessInstanceByKey gives the instance back ?

jbarrez — Thu, 06 Dec 2012 16:20:23 GMT

Maybe this should be mentioned very early in the docs…

I don't know … async is a pretty complex thing to grasp …
Definitely if you don't understand the regular transactional way of execution …

If i put "async = true" then it doesn t find my class "com.test.ActivitiTask" and doesn t lauch my method execute…

Huh? The jobexecutor (which runt he async jobs) lives in the same JVM as the engine …
It doesn't execute it immediataly of course. And also, you have to make sure the jobexecutor is actually activated in the process engine configuration.

Re: When startProcessInstanceByKey gives the instance back ?

vire7777 — Fri, 07 Dec 2012 09:38:42 GMT

I've putted jobExecutorActivate on "True" but nothing else !
Anyway i really doesn't unsderstand why it doesn't find my class and i have a "class not found" error message however when the task isn't async, it works perfectly.
I've read the doc and there's nothing about it… I understand how it works and that s why i m so disapointed…

Other question :
Could it be possible that, because i'm deploying my xml on activiti-explorer, when i lauch the process instance and engine in my application (not activiti explorer), activiti try to search my class (in the async javaservicetask) in activiti-explorer evenif i really don't think so (logically, it would search, as you said, in the same JVM)

Re: When startProcessInstanceByKey gives the instance back ?

ronald_van_kuij — Fri, 07 Dec 2012 09:49:47 GMT

Maybe this should be mentioned very early in the docs…

I don't know … async is a pretty complex thing to grasp …
Definitely if you don't understand the regular transactional way of execution …

Just a reference that if you want/actually need something like this, making the first task async is needed. Point out that it is 'advanced' usage, and just point to the async chapter… Nothing more

Re: When startProcessInstanceByKey gives the instance back ?

ronald_van_kuij — Fri, 07 Dec 2012 09:52:15 GMT

Other question :
Could it be possible that, because i'm deploying my xml on activiti-explorer, when i lauch the process instance and engine in my application (not activiti explorer), activiti try to search my class (in the async javaservicetask) in activiti-explorer evenif i really don't think so (logically, it would search, as you said, in the same JVM)

Yes… classes should be available to ALL jvm's that do something on the process… If the job executor is in the explorer and the classes are not, you get this error.

Re: When startProcessInstanceByKey gives the instance back ?

vire7777 — Fri, 07 Dec 2012 10:10:22 GMT

I thought the job executor was created with the creation of the process engine instance, not at the xml deployment
Anyway, i ll do a test

Re: When startProcessInstanceByKey gives the instance back ?

ronald_van_kuij — Fri, 07 Dec 2012 10:34:43 GMT

The explorer also has a process engine…