Since upgrading from 6.x to 7.1.2 we are unable to edit pages created prior to the upgrade. New pages can be created and edited.
This is what I see in the log when a user tries to edit a page:
2020-01-30 12:31:45,631 WARN [http-nio-8090-exec-7] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doRollback Performing rollback. Transactions:
->[null]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT (Session #70385150)
-- url: /pages/editpage.action | page: 65573 | traceId: 194710e91872e937 | userName: myuser | referer: https://confluence.mydomain.com/display/OI/mydomain+IT | action: editpage
2020-01-30 12:31:45,637 WARN [http-nio-8090-exec-7] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doRollback Performing rollback. Transactions:
->[com.atlassian.confluence.pages.DefaultPageManager.createOrFindDraftFor]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT (Session #70385150)
-- url: /pages/editpage.action | traceId: 194710e91872e937 | userName: myuser | referer: https://confluence.mydomain.com/display/OI/mydomain+IT
2020-01-30 12:31:46,258 WARN [http-nio-8090-exec-1] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doRollback Performing rollback. Transactions:
->[null]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT (Session #456536595)
-- space: 98306 | url: /plugins/editor-loader/editor.action | page: 65573 | traceId: b590e27ccd306e52 | userName: myuser | referer: https://confluence.mydomain.com/pages/viewpage.action?pageId=65573&editingFailed | action: editor
2020-01-30 12:31:46,263 WARN [http-nio-8090-exec-1] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doRollback Performing rollback. Transactions:
->[com.atlassian.confluence.pages.DefaultPageManager.createOrFindDraftFor]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT (Session #456536595)
-- url: /plugins/editor-loader/editor.action | traceId: b590e27ccd306e52 | userName: myuser | referer: https://confluence.mydomain.com/pages/viewpage.action?pageId=65573&editingFailed
I have tried repairing the ancestors table which seemed to be a solution for a similar problem, but that did not work. Does anyone know anything else we might be able to try to "repair" these "old" pages?
