-
Type:
Bug
-
Resolution: Incorrectly Filed
-
Priority:
Highest
-
None
-
Affects Version/s: 7.20.3
-
Component/s: Search - Indexing
-
None
-
Severity 2 - Major
Issue Summary
The post reindex completion bug reported in ticket CONFSERVER-81685 which has been fixed in Confluence version 7.19.6, seems to be back again in version 7.20.3 as reported by customer data:
2023-05-27 03:06:27,893 ERROR [Indexer: 2] [engine.jdbc.spi.SqlExceptionHelper] logExceptions You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') or contentent0_.CONTENTID in ()) and contentent0_.CONTENT_STATUS='current'' at line 1
2023-05-26 11:15:11,893 WARN [http-nio-8080-exec-33 url: /rest/api/content/886523241; user: xxxxxxxxxxx] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doRollback Performing rollback. Transactions: 103962 ->[com.atlassian.confluence.api.impl.service.content.draft.ContentDraftServiceImpl.publishEditDraft]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT (Session #2017201714) 103963: [null]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT,readOnly (Session #1936438804)
Steps to Reproduce
- Step 1 Disable Collaborative Editing or ensure there are personal drafts already under the database. If personal drafts are available, skip step 2 below.
- Step 2 Create a page and a draft under Confluence.
- Step 3 Trigger rebuild from UI
Expected Results
No SQL Errors should be reported during normal index processing and 100% completion should be reported under atlassian-confluence-index.log file.
Actual Results
Logs are flooded with SQL-related errors.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- links to