We are recently having some problems with the updates on Bandana table within a transaction.
In some processes we can have some updates statements to Bandana and it reaches a moment that we lock the database, having to kill the process in order to Confluence works properly.
We are wondering if there are some restrictions in the number of accesses that we can make to Bandana in a single transaction, and if not, we’d like to know what could be causing this problem
Thanks for the feedback, Gorka. We’re currently investigating an issue where updates to the Bandana table within a transaction can cause the database to lock, preventing Confluence from functioning properly. We’re wondering if there are any restrictions in the number of accesses that can be made to Bandana in a single transaction, and if not, what could be causing this problem. We’ll update you as soon as we have more information.
Can you please share with me what version of Confluence have you tested? What database and its version?
Can you also share one example of your plugin that can help reproduce the problem?