topic job executor failed to process all jobs in Alfresco Archive

job executor failed to process all jobs

tonyado — Mon, 29 Aug 2016 09:09:01 GMT

FYI. I am running async service task test, and my unit test code is:<blockcode>public void testParallel() throws Exception { final String deploymentId = repositoryService.createDeployment().addClasspathResource("ParallelServiceTask.bpmn20.xml") .deploy().getId(); S

Re: job executor failed to process all jobs

warper — Mon, 29 Aug 2016 09:53:23 GMT

Hi!
It seems you did not enable job executor: jobExecutorActivate=false in your settings.

Re: job executor failed to process all jobs

tonyado — Mon, 29 Aug 2016 11:06:14 GMT

hi Wraper, I just tried to set <code>jobExecutorActivate=true</code>, it has no help with this. Still the same problem. And according to the user guide, this value should be false imo.

Re: job executor failed to process all jobs

warper — Mon, 29 Aug 2016 12:47:45 GMT

Hi TonyAdo,
Currently you might experience issues with parallel gateway due to "exclusive=false" in your tasks definitions.
Please take a look at activiti user guide, section 8.7.3. Exclusive Jobs. In particular, it mentions your scenario:

Why is this a problem? Since the service tasks are configured using an asynchronous continuation, it is possible that the corresponding jobs are all acquired at the same time and delegated to different worker threads by the JobExecutor. The consequence is that the transactions in which the services are executed and in which the 3 individual executions arrive at the parallel join can overlap. And if they do so, each individual transaction will not "see", that another transaction is arriving at the same parallel join concurrently and thus assume that it has to wait for the others. However, if each transaction assumes that it has to wait for the other ones, none will continue the process after the parallel join and the process instance will remain in that state forever.

Also, please make sure jobExecutor actually runs and executes jobs. Even if process stalls at parallelgateway you should see two executions at about this stage of process.

Re: job executor failed to process all jobs

tonyado — Mon, 29 Aug 2016 13:25:16 GMT

Hi, Wraper

Thanks for your detailed reply. But if I remove <code>exclusive=false</code>, the service tasks are executed in sequence not in real parallel. From the test output:
<blockcode>
Mon Aug 29 21:21:24 CST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
deployment id: 1
Mon Aug 29 21:21:26 CST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Mon Aug 29 21:21:26 CST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
start download bundle service task: 26
start off traffic service task: 26
download bundle get executed
off traffic get executed

org.activiti.engine.ActivitiException: time limit of 30000 was exceeded

at org.activiti.engine.impl.test.AbstractActivitiTestCase.waitForJobExecutorToProcessAllJobs(AbstractActivitiTestCase.java:213)
at com.westudio.activiti.ParallelServiceTaskTest.testParallel(ParallelServiceTaskTest.java:20)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at org.activiti.engine.impl.test.PvmTestCase.runTest(PvmTestCase.java:65)
at junit.framework.TestCase.runBare(TestCase.java:141)
at org.activiti.engine.impl.test.AbstractActivitiTestCase.runBare(AbstractActivitiTestCase.java:86)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:117)
at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:253)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)

Process finished with exit code 255
</blockcode>
we can see service tasks really get executed, the problem is job executor will exceeded the time limit, and the process will never reach to the end state.

Re: job executor failed to process all jobs

warper — Mon, 29 Aug 2016 14:00:04 GMT

Hi TonyAdo!
Well, it's expected to be so. Each execution updated its own transaction and doesn't see data from another transaction. To see it they need to be run in one transaction context and it happens only if they already run in exclusive mode.
To be honest, I've never joined non-exclusive executions.
I think you can add dummy script tasks with asynch=true and exclusive=true flags after your service tasks and they will go to parallel gateway and join properly. It will take a couple more async jobs, but theorethcally it should fix the issue.

Re: job executor failed to process all jobs

tonyado — Tue, 30 Aug 2016 00:04:33 GMT

Thanks Wraper, I will give a try to see whether it works.