Timeout when engine resuming

Description

Hi,

The issue is related to the process dependencies resolution. It is executed every time the engine is paused and then resumed. The big number of processes (mote than 150 in my case) is causing trasaction timeout, because dependencies resolution is executed for all the process in one transaction. The default transaction time limit is set to 60 seconds and can be increased. However it can be increased only globally and that can be bad for stability and performance. Do you think it is reasonable to break this single transaction to separate transactions for every process and resuming tenat as well?

Environment

None

External Link

None

Workaround

You can workaround this problem by setting timeout to higher value. After resuming tenant it can be decreased. However it requires server restarts.

Activity

Show:
Antoine Mottier
December 16, 2019, 6:01 PM

Hi Maciej,

Sorry for the late answer. I got some clarification from our R&D team and actually prior to version 7.9.0 loading of process dependencies was done in one single operation when starting or resuming Bonita Engine. That was causing issue as you described. But since 7.9.0 the process dependencies are loaded only on the first access of each individual process definition. This new behavior should prevent performance issue as you report in this issue.

I’m confused about the affected versions you set fort this issue. Can you confirmed that you still face this issue on 7.9.4?

Thanks

Maciej Michalak
February 20, 2020, 1:52 PM

Hi Antoine,

Sorry, I must have missed your answer.

The issue originally have occured on 7.9 version of production environment. I have also reproduced it locally on 7.5.4, that is why I set both versions in the current ticket.

I believe you meant 7.10 is the version in which it was fixed. I didn’t verified it yet, but I see changes in the engine’s code which affect dependencies resolving.

Antoine Mottier
February 26, 2020, 2:14 PM

Actually you are right the last update regarding this issue is available since 7.10.0 ( )

So I recommend to update to 7.10.0 to fix this issue.

Is it possible for you to do this upgrade?

Delphine Coille
November 4, 2020, 11:06 AM

I was reviewing issues and I see this one is still waiting for your confirmation; have you finally udgraded to 7.10 ?

Thanks

Maciej Michalak
November 5, 2020, 10:42 AM

Hi Delphine,

 

The project with this issue was not developed for a while and there was no urgency for upgrade. If it is already solved, you can close this ticket.

Assignee

Delphine Coille

Reporter

Maciej Michalak

Affects versions

Reference

None

Fix versions

None
Configure