Same problem here since several days, using Confluence Cloud. Please reopen this.

Problem is again, present in V. 7.13.4 - pls reopen this issue. 

Hello together,

I can´t really see a solution for this issue so why is it closed?

I demand for an answer

for our problem, we used workaround to change the Collaborative Editing to Limited in Admin panel. that allowed use to edit the pages. 

To resolve our issue, we found out that commons-lang3-3.9.jar file was not at it's default location of [ConfluenceHome]/synchrony-proxy/WEB-INF/lib. Verify if that jar file is there. we moved the file to right location our issue was resolved the issue.

Same problems here. We use it as a server version and have about 800 users. 

Can you tell us when there will be the next bugfix?

Starting to see this problem crop up too, was there any fix?

The publishing software can't publish. And this ticket is closed? Is this going to be fixed ever? Or it is time to switch platforms now?

hello i have this problem on a Confluence cloud installation of about 500 users, when do you plan to solve it forever

Hi, 

I contacted the Atlassian support regarding this issue and its frequency, and they told me that it could be related to the migrations from the legacy Confluence editor to the new one. In fact, below is their answer:

New page editor on Confluence creates but does not close connections to Synchrony during single page app transitions when viewing and editing pages. These transitions stack connections over time, consuming the available connection pool in the Synchrony cluster. Monthly active users for the new editor has increased as the Confluence team have progressed their rollout.

Synchrony is the service that runs the collaborative editing features in Confluence. As far as I can tell, the increased load due to the gradual migration of the new editor was unexpected. Our developers are aware of the issues and have mentioned the corrective actions:

• Clean up logging(reduce noise) to make early detection easier
• Increase number of metrics measuring new editor rollout events - helps with root cause analysis
• Verify exponential backoff functionality in the client works as expected - should be already be working
• Enhancement and further review of the capacity planning around the migration

On my side, I sometimes continue to experience this issue, and the workaround mentionned in this bug report (refreshing the page each time this happens) still works. But it is very annoying when I realize that not all the modifications made are not taken into account after refreshing. 

Could you please open another Bug Report / reopen this one, in order to minimize (or cancel) the effects of migrations to the new editor on our sites?

Thanks in advance.

I am getting a similar issue. Creating a new page using the + button on the navigation bar is fine, however when I edit an existing page and enter a link to a page I want to create new, this is where I encounter an issue. Refreshing does not resolve this problem either, so I have to create using the 'c' or '+' sign. Not a huge problem for me but still a little irritating. I'd prefer incremental feature delivery than lower priority niggles like this. It does stress out inexperienced Confluence users though, but I do my best to help them out.