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.

TransactionManagement and async=true

rene

HI,

we are very puzzled about the transactions in Activiti. While testing we got other results than the documentation suggested when we use activiti:async="true".

By the documentation i understand that every time activiti:async="true" is configured the actual transaction is committed and a new one is created by the jobExecutor, right? That is true if you have two ServiceTask configured. In my test project i faced the following limitation to this behaviour.

1.) activiti:async="true" for a SubProcess is does not lead to a new transaction
2.) If you have more than one ServiceTask with activiti:async="true" in a row this only applies to the first activiti:async="true" configured.

Am I missing something? I hope you can help me on this. I faced the same issue in Version 5.12 and 5.14.

My config does look as follows:

    @Bean
    public SpringProcessEngineConfiguration processEngineConfiguration() {
        final SpringProcessEngineConfiguration engineConfiguration = new SpringProcessEngineConfiguration();
        final DataSource dataSource = activitiDataSource();

        engineConfiguration.setDataSource(dataSource);
        engineConfiguration.setTransactionManager(transactionManager);
        engineConfiguration.setDatabaseSchemaUpdate("drop-create");
        engineConfiguration.setJobExecutorActivate(true);

        return engineConfiguration;
    }
‍‍‍‍‍‍‍‍‍‍‍‍‍‍

where the transaction manager is used for Activiti and my application db.

When needed I can provide a test project to verify my result.

Any help will be appreciate! thanks in advance,

Rene

Find more posts tagged with

Comments

martin_grofcik

Hi Rene.

Could you attach jUnit test (or project) please?

Regards
Martin

rene

Hi Martin,

thanks for you reply, I have created a simple project thats demonstrates the second "async" in a row issue. I hope you can help us with this issue.

If you have any questions about the project, let me know.

Thanks a lot,

Rene

PS: since i can attach only txt files, i added the extension to txt. 🙂

activiti-transactions.zip_.txt.zip

martin_grofcik

Hi Rene,

Thank you for very clearly defined problem.

I had a look on the de.wps.activiti.process.TransactionExceptionThrowingProcessTest2Async#transactionManagementTest test.
I found that there is no wait to finish asynchronous tasks. I changed test little bit.

<br> @Test<br> @Deployment(resources = { PROCESS_BPMN })<br> public void transactionManagementTest() throws Exception {<br>&nbsp; try {<br>&nbsp;&nbsp; runtimeService.startProcessInstanceByKey(PROCESS_KEY, key);<br>&nbsp; } catch (Exception ex) {<br>&nbsp;&nbsp; LOGGER.error("#### Catched exception ####", ex);<br>&nbsp; }<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TimeUnit.SECONDS.sleep(15);<br>&nbsp; assertThat(countHistoricProcessesByBusinessKey(key), is(1L));<br>&nbsp; List<Foo> findAll = fooRepository.findAll();<br>&nbsp; assertThat(findAll, containsInAnyOrder(hasProperty("bar", is("FooBar1")), hasProperty("bar", is("FooBar2"))));<br><br>&nbsp; assertThat(findAll.size(), is(2));<br> }<br>

TimeUnit.SECONDS.sleep(15) waits for job executor to process all jobs. JobExecutor is invoked periodically, that's why we have to wait on it to be executed.
There is 3 times retry set by default. That's why jobexecutor tries 3 times to execute changeDBValueTo3
Wait can be done in more elegant way - activiti tests use

<br>&nbsp; public void waitForJobExecutorToProcessAllJobs(long maxMillisToWait, long intervalMillis) {<br>&nbsp;&nbsp;&nbsp; JobExecutor jobExecutor = processEngineConfiguration.getJobExecutor();<br>&nbsp;&nbsp;&nbsp; jobExecutor.start();<br><br>&nbsp;&nbsp;&nbsp; try {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Timer timer = new Timer();<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; InteruptTask task = new InteruptTask(Thread.currentThread());<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; timer.schedule(task, maxMillisToWait);<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; boolean areJobsAvailable = true;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; try {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; while (areJobsAvailable && !task.isTimeLimitExceeded()) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thread.sleep(intervalMillis);<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; try {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; areJobsAvailable = areJobsAvailable();<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } catch(Throwable t) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Ignore, possible that exception occurs due to locking/updating of table on MSSQL when<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // isolation level doesn't allow READ of the table<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } catch (InterruptedException e) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // ignore<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } finally {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; timer.cancel();<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (areJobsAvailable) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; throw new ActivitiException("time limit of " + maxMillisToWait + " was exceeded");<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br><br>&nbsp;&nbsp;&nbsp; } finally {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jobExecutor.shutdown();<br>&nbsp;&nbsp;&nbsp; }<br>&nbsp; }<br>

Please let me know whether it helps.

Regards
Martin