I've been battling this issue for some time now, but basically our Confluence instance will be stable and happy running for many months at a time with no changes to the JVM memory size and then suddenly I get a problem where the GC cannot recover enough memory. This makes Confluence inaccessible for all users as it doesn't respond.
From the GC logs I cannot see a trend in the memory usage that would warn me this is about to happen, it just suddenly stops being able to recover enough memory.
I have increased the maximum memory pool for the Confluence service so I'm now at 3840 MB, but as I increase this it obviously creates a bigger load on the server when it hits the limit again.
Some example data below
This has been identified to be caused by the File Conversion plugin, which has a memory leak and causes the available Java Heap space to fill up and then kills our server as it tries to recover it on GC.
We've tried up to 10GB Heap and this is still an issue so we've disabled the File Conversion plugin until this is fixed.
No idea when this will be fixed, but disabling the plugin reduces the functionality of Confluence for us, we were relying on this preview for collaborating on documents, or just easy preview of embedded documents.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Community, Jessica here from the Confluence Product Marketing team! July’s community challenge is all about sharing pictures — and as an extension of our first post on what ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs