We've been having MANY problems with editing and believe it's related to Synchrony. Users couldn't edit or couldn't save what they edited and got an error message that Confluence wasn't responding and to check with an administrator.
One of the solutions was to restart Synchrony. On one instance (We have three instances of Confluence.), I tried the restart suggestion and also turned off collaborative editing and tried to turn it back on. That resolved the problem a few times in the past, but now, it won't let me turn it back on.
We also thought the maximum heap size might have been one of the problems and that there wasn't space. Our webmaster worked on the space problem and also increased the maximum heap size from 2GB to 4GB. Now, not only can I not turn the collaborative editing back on, the maximum heap size is showing only 2 GB in the Confluence admin panel, yet showing 4 GB on the server, according to our webmaster.
Now, we're having similar problems with a second instance of Confluence, with page editing and uploading files. One of my teammates reset Synchrony and it seems to be working, but I'm afraid to turn it off due to the problem I have with the first instance. The heap size on that instance was increased from 2 GB to 4 GB and is still showing 4 GB on the Confluence admin panel.
The third instance has been a problem as well with uploading attachments, but that has been with a custom plug-in. Since we're on "maximum telework" and the third instance is a classified system, I'm not aware of general problems with uploading documents. However, in light of the first two instances, I can't help but wonder if it's Confluence and Synchrony that is causing the upload problems with the custom application inside Confluence.
These problems started with the upgrade to Confluence v. 7.13.0 in early September. Are you aware of some bug that may be causing this?
Thanks.
I would suggest having your admin look at the KB article https://confluence.atlassian.com/conf713/performance-tuning-1077914666.html
What you are describing sounds like an issue with how much RAM you have on the server and how much of that is allocated to Confluence. You should be able to see errors in the log when you turn on collaborative editing and it fails. I would suggest starting there. Also if you are only seeing 2gig in the application that is all that is allocated to the app. Here is how to increase memory https://confluence.atlassian.com/confkb/how-to-fix-out-of-memory-errors-by-increasing-available-memory-154071.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.