Baselines create a multiple definition error

Implementation

• In 3.6.6, we’ve removed some features of our caches, which were too complex to be accurately maintained. We didn’t lose much performance, because it is now a background job.

• In 3.6.7, we’ve added an upgrade task to cleanup the inconsistent records.

• We are still waiting for informations from customers to better diagnose the issue.

Explanation

With the version 1 engine, it may happen that we create baselines from cached pages, this might be what is causing the issue. The user cannot go to version 2 because there are different features and they won’t be able to compare baselines.

Original description

The users are creating baselines from the page and when doing so, they receive an “error: NullPointerException: null. The baseline is an error and should be deleted.” All requirements of the page are highlighted in red and appear as there is a multiple definition. When clicking on the second original page, it goes to a previous version in the page.

App version : 3.6.1

Indexing engine: Version 1

Confluence Version: 7.19.8