Confluence 7.17.1 crashes by transaction PluginReadWriteTx

w_v_krimpen_slootweg
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 10, 2022

Server runs out of memory (Java VM heap) and freezes. In logging found:

WARN: [Caesium-1-2] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doRollback Performing rollback. Transactions: ->[PluginReadWriteTX]: PROPAGATION-REQUIRED,ISOLATION_DEFAULT (session #561381725)

ERROR: [Caesium-1-2] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job com.atlassian.confluence.plugins.confluence-edge-index:flushEdgeIndexQueueJob#flushEdgeIndexQueue failed to run com.atlassian.bonnie.LuceneException: org.springframework.transaction.UnexpectedRollbackException: Transaction rolled back because it has been marked as rollback-only

2 answers

1 vote
Ilkka Kiiskinen June 16, 2022

We have the same issue with multiple different instances with different users and add-ons. We have both docker and linux binary installations. Issues started when upgraded to 7.17.x versions.

We have an open issue to Atlassian support. Please open a support ticket to Atlassian to get more attention to this and to get support more data to find the root cause. Prepare your system to take java heap dumps.

We have already increased heap memory, but that seems not to be the solution.

Logs led us to this KB article: https://confluence.atlassian.com/confkb/confluence-logs-filled-with-the-error-failed-to-process-edge-index-task-838403476.html

We followed the instructions and rebuilt the content index from scratch including the optional step to restore popular content. https://confluence.atlassian.com/confkb/how-to-rebuild-the-content-indexes-from-scratch-on-confluence-server-110035351.html

Edge index errors stayed away only for awhile, so even this does not really fix the issue.


I hope we get some fix to this soon from Atlassian.

0 votes
Robin Peters
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 21, 2022

We now have the same problem with 7.17.4. Started suddenly today and still occurs and crashing our instance. I will raise support ticket for this asap.

Some of you found a solution so far?

Robin Peters
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 23, 2022
Ilkka Kiiskinen June 23, 2022

At least in our case, this was not a permanent fix. Happened again after some time.

Siva Krishna Bhusarapu
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 23, 2022

We as well running into similar kind of issue with 7.17.2 and we have a open ticket with atlassian.

Tommy van Extel July 28, 2022

Hi Siva, did you get a fix / answer from Atlassian?

Siva Krishna Bhusarapu
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 28, 2022

Hi Tommy, They are aware of the issue and they are working on fix but didn't provide any ETA. https://jira.atlassian.com/browse/CONFSERVER-79529  suggested to do Rebuild index from scratch but its not helping much.

Like Tommy van Extel likes this
Tommy van Extel July 28, 2022

Thank you for your reply

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
7.17.1
TAGS
AUG Leaders

Atlassian Community Events