Under General Configuration - Collaborative Editing, check the Synchrony service to see if it is running.
I had the same issue, and the service had failed.
I ended up upping the memory for it from 2GB to 4GB and it has been working fine since.
Change will take affect on next restart of Confluence.
- Stop Confluence.
- To do that, open up a terminal window and browse your way to the Confluence-Installation-Directory/bin folder.
- Inside this very same folder, run the following command: ./stop-confluence.sh
- Just consult with your team first to understand if this is the script usually used or if you have customized a different one based upon your needs. If this is the case, run the customized one.
- Now that we stopped Confluence, under the same Confluence-Installation-Directory/bin folder, look for a file called setenv.sh.
- Open this file.
- Search for synchrony.memory.max. If you have this setup, just change its value to an appropriate allocation.
- If you don't have this setup, it means that the default Heap Allocation for Synchrony was applied, which, in this case, is 2GB for versions above 7.10 and 1GB for versions below it. We need to add the parameter to change the Heap Allocation. The example below sets it to 2GB, change the number to allocate as many GB's as you may need to.
CATALINA_OPTS="-Dsynchrony.memory.max=2g ${CATALINA_OPTS}"
- With that done, still inside Confluence-Installation-Directory/bin, run the ./start-confluence.sh script. Don't forget to consult with your team to understand if you have customized scripts or not. In case you do, run your customized one. In case you don't, run the mentioned one.
- Confluence will come up with Synchrony having the new allocated Heap.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.