logAncestorsTableFailure after create spaces and pages in Confluence

[Orkun Gedik]

I am working on a confluence plugin which creates spaces and pages via Java API. When I check my confluence-logs, I am facing with an log on ERROR level;

ERROR [http-nio-6700-exec-2] [persistence.dao.hibernate.HibernateContentPermissionSetDao] logAncestorsTableFailure Detected ancestors table corruption for pageId: 1901470. Access to this page is blocked for all users as inherited permissions cannot be determined. To resolve this, rebuild the ancestors table. See https://confluence.atlassian.com/display/DOC/Rebuilding+the+Ancestor+Table

 I have no idea why I am taking this error. Any suggestions or tips will be helpful.

[Madhusudhan Matrubai · Accepted solution]

Probably this https://confluence.atlassian.com/doc/rebuilding-the-ancestor-table-153948.html can fix your problems.

Good luck..

Thanks,
Madhu

[Al Johnson]

We are experiencing the exact same issue.  It happens again every time after rebuilding the ancestor table so that is not solution.

@Orkun Gedik Did you find a workaround or some other solution?  I am saving like this for new pages:

    glossaryPage.setBodyAsString(sb.toString());
    pageManager.saveContentEntity(glossaryPage, null);

And like this for pre-existing pages:

    SaveContext saveContext = DefaultSaveContext.DEFAULT;
    glossaryPage.setBodyAsString(sb.toString());
    pageManager.saveContentEntity(glossaryPage, oldGlossaryPage, saveContext);

------

There is also this critical bug reported: CONFANCESTORS table obtains duplicate record after a page page re-order to space root

which i cannot reproduce, but it may be related.

Confluence 6.6.7, clean install, local ATLAS developer instance, no other plugins/add-ons installed.

[Al Johnson]

I solved this problem by explicitly setting many fields of the Java objects for the new page relating the space, page and parent page, such as setting the parent of the child and child of the parent, space of the child, etc..

[Antonio Dionisio]

I had the same problem when creating the pages programatically. I have found that calling this method after the child page creation fix the problem:

pageManager.updatePageInAncestorCollections(page, parentPage);

[Adrian Moerchen]

There is something wrong, if there is a method explicitly for this...

I also had to call 

parentPage.addChild(page);