Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Confluence 7.17.1 crashes by transaction PluginReadWriteTx


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

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:

We followed the instructions and rebuilt the content index from scratch including the optional step to restore popular content.

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

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?

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

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

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

Hi Tommy, They are aware of the issue and they are working on fix but didn't provide any ETA.  suggested to do Rebuild index from scratch but its not helping much.

Like Tommy van Extel likes this

Thank you for your reply

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events