Time out exception


Im trying to delete a very large case and the rest api is giving me a QueryTimeoutException.

Im not sure if for this case I have to modify the database time out setting or if there is a way to modify the Bonita Rest API time out.

Hope someone could help me out.


1 answer

This one is the BEST answer!


To solve this issue you might want first try to update to Bonita 7.8.0 as some improvement has been done on performance of deletion of archived cases (see changelog).

Also I guess that QueryTimeoutException actually refer to an SQL query that taking to long to run based on the settings of the database. So increasing the timeout in the database configuration might fix this issue. In order to make sure this timeout is related to the database can you share with me the full Bonita Engine log file using for example Google Drive, Dropbox...



Submitted by mzhu on Thu, 01/17/2019 - 21:08

Hi Antoine,

Thanks a lot for your response, we have a heavy log file so it was dificult for me to share the full log, instead Ill share a fragment with the sql QueryTimeoutException that I mentioned.


Submitted by antoine.mottier on Mon, 01/21/2019 - 10:00

Ok so based on the exception in the log I can confirm that this is an issue related to the duration of the execution of the SQL query in charge of deleting process instance.

So my advise here would be to upgrade to 7.8.0.


Submitted by mzhu on Mon, 01/21/2019 - 18:09

The improvement made to case deletion apply to open cases too?
After reading the changelog it says that some events are not triggered anymore "ARCHIVED_FLOWNODE_INSTANCE_DELETED" does that mean that it will not delete the records of the table arch_flownode_instance anymore? because we are trying to reduce the size of that table.

And again, thanks a lot for your time Antoine,


Submitted by antoine.mottier on Mon, 01/21/2019 - 18:33

It applies to all process instances (cases) that have finished nodes. So it will impact the deletion of open cases.

The data is still deleted in the database, the change is that now we no longer trigger the event ARCHIVED_FLOWNODE_INSTANCE_DELETED and so we manage to do the deletion faster (less processing related to the deleted event).