topic Re: Java Service Task custom asynchronous behaviour: Complete task using signal or callback. in Alfresco Archive

Java Service Task custom asynchronous behaviour: Complete task using signal or callback.

saraiva — Tue, 10 May 2016 13:00:24 GMT

Hello, this has already been answered but the solutions have not been working out for me.Activiti asynchronous behaviour is fairly simple and only allows the user to enable a flag which tells activiti engine to insert such task in a execution queue (managing a pool of threads).What i want is not to

Re: Java Service Task custom asynchronous behaviour: Complete task using signal or callback.

saraiva — Tue, 10 May 2016 13:35:10 GMT

To further clarify my issue. I attempted to signal the runTimeService directly in the callback:

<code>
processEngine.getRuntimeService().signal(execution.getId());
</code>

However, as i previously said, the engine no longer holds my process.

<code>

org.activiti.engine.ActivitiObjectNotFoundException: execution 4160010 doesn't exist
at org.activiti.engine.impl.cmd.NeedsActiveExecutionCmd.execute(NeedsActiveExecutionCmd.java:48)
at org.activiti.engine.impl.interceptor.CommandInvoker.execute(CommandInvoker.java:24)
at org.activiti.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:57)
at org.activiti.engine.impl.interceptor.JtaTransactionInterceptor.execute(JtaTransactionInterceptor.java:65)
at org.activiti.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:37)
at org.activiti.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:40)
at org.activiti.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:35)
at org.activiti.engine.impl.RuntimeServiceImpl.signal(RuntimeServiceImpl.java:278)
at pt.ptinovacao.na.swe.testcase.bpm.base.tests.activiti.test.customAsyncTask$$anonfun$execute$1.apply(custom.scala:83)
at pt.ptinovacao.na.swe.testcase.bpm.base.tests.activiti.test.customAsyncTask$$anonfun$execute$1.apply(custom.scala:75)
at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32)
at scala.concurrent.impl.ExecutionContextImpl$AdaptedForkJoinTask.exec(ExecutionContextImpl.scala:121)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.pollAndExecAll(ForkJoinPool.java:1253)
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1346)
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

</code>

Re: Java Service Task custom asynchronous behaviour: Complete task using signal or callback.

saraiva — Tue, 10 May 2016 13:42:29 GMT

And to further clarify this is where returning null both using runTimeManager directly or a customSignal

<code>
val execution = commandContext.getExecutionEntityManager.findExecutionById(executionID)
</code>

Re: Java Service Task custom asynchronous behaviour: Complete task using signal or callback.

jbarrez — Wed, 18 May 2016 15:45:58 GMT

Really hard to say what you're trying to do here … any chance you can wrap it up it in a unit test.

But from what i'm seeing, is that you do a leave() in the execute()? You can't use leave() if you later expect a signal() to be executed. If you want to do wait behaviour, you need to remove the leave().