要約

The page properties report is not showing all the pages with the page properties macro and proper label. Also, it is exhibiting strange behavior in a way that once some page is updated without making any changes, it starts showing up under the report for a few days. 

環境

Confluence version 7.4.7

診断

The below errors can be seen under the atlassian-confluence.log when we try to load Page Properties Report Macro; these errors are repeated for each page. 

java.lang.IndexOutOfBoundsException: Index 1 out of bounds for length 1
        at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
        at java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
        at java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)

and post this, we can see below errors for other pages 

java.lang.IllegalStateException: Stopwatch already started.
        at org.apache.commons.lang3.time.StopWatch.start(StopWatch.java:233)

原因

This happens since Page Properties Report Marco tries to capture all the page properties macro and as a part of processing these macros, it tries to check whether the headings are in vertical order or horizontal (default) so that it can parse and provide the information. Now, in a scenario where the table added under Page Property Macro does not conform to either horizontal or vertical heading, the report will not be able to parse it and will throw the above errors. Watch out for the first error while loading the report and as a part of that error, the storage format of the table would be printed. Use this storage format of the table and try to load it locally to check if the table is missing any horizontal or vertical headings or columns. An example:

ソリューション

There are 2 options to resolve this problem:

Option 1: Remove the tables from the Property Page Macro that don't conform to Page Property Macro around horizontal heading or vertical heading and then try running the report again

Option 2: Align the page property macro boundaries horizontally and vertically so that they can be parsed by the report fine.