Viewing a page causes "Unable to resolve owner of loading collection" error message in Confluence
Platform Notice: Server and Data Center Only. This article only applies to Atlassian products on the server and data center platforms.
Viewing a page shows the following error in logs.
2020-05-04 23:07:05,044 ERROR [http-nio-8080-exec-13] [atlassian.confluence.servlet.ConfluenceServletDispatcher] sendError Could not execute action -- url: /pages/viewpage.action | traceId: 1273a70858101de8 | userName: admin | referer: http://localhost:8090/login.action?os_destination=%2Fpages%2Fviewpage.action%3BRelease%2BNote%2BCreation%2BStandards%2Band%2BGuidelines&permissionViolation=true java.lang.RuntimeException: Error rendering template for decorator root at com.atlassian.confluence.setup.velocity.ApplyDecoratorDirective.render(ApplyDecoratorDirective.java:162) . Caused by: org.hibernate.HibernateException: Unable to resolve owner of loading collection [[com.atlassian.confluence.core.ContentEntityObject.contentProperties#152548091]] for second level caching at org.hibernate.engine.loading.internal.CollectionLoadContext.addCollectionToCache(CollectionLoadContext.java:321)
In some cases the error can happen on some other actions in Confluence as well. Though, as long as the cause of the error is the same we can proceed with the resolution here.
A couple of causes have been identified for this issue:
- Confluence is unable to load a data element from the cache. In the example above, this would correspond to contentProperties table for the ContentID column where ID 152548091 that's noted in the logs.
- Another possible cause is a conflict with a third party plugin.
To address the first possible cause, try clearing Confluence's cache which should force a refresh of the page:
- Log into the admin console > General Configuration > Cache Management
- Select Flush all at the bottom of the page
To verify whether this is plug-in relate, temporarily enable safe mode during a maintenance window or down time and seeing if the page renders. If the page does render, then reenable the third party plugins one by one and retest the page each time to see which plugin causes the page to not display as expected.
If neither of these steps help, then another option would be to rebuild the indexes of the system using steps provided in Content Index Administration.