[CONFSERVER-45599] Collaborative Editing fails to start with 502 Bad Gateway (or 404) errors for sockjs.min.js, synchrony.min.js when Confluence is running in a zh_CN.UTF-8 (or other non en_GB) locale Created: 19/Dec/2016 Updated: 14/Feb/2018 Resolved: 07/Feb/2017
|Component/s:||Editor - Collaborative editing|
|Affects Version/s:||6.0.1, 6.0.2, 6.0.3, 6.0.4|
|Reporter:||James Richards||Assignee:||Vivian Hu|
|Labels:||affects-server, cloud-ignore, enterprise, warranty|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Attachments:||502BadGateway.png Region&language.png SetAsDefault.png Settings.png Time&language.png|
|Support reference count:||16|
|Last Touched By:|
|Last commented:||1 year, 1 week, 6 days ago|
|Sprint:||Enterprise is nifty, Enterprise is optimal, Enterprise is pleasing|
Although the fix is for a Windows server, we should test it against Confluence running on Linux or Mac OS to avoid any regressions. Once it's set, collaborative editing should work as expected.
Fix for locale:
Make sure to carry out a manual test end to end of the collaborative editing feature when the fix is in. i.e. starting Synchrony, Confluence and editing a page.
|QA Demo Status:||Not Done|
|QA Kickoff Status:||Done|
When using Confluence 6.0 with Collaborative editing enabled on a Server with non-Western locale we see
Synchrony-proxy uses Jetty Proxy to handle HTTP requests/responses, and it only recognizes a certain range of characters as legal. Synchrony's date formatter uses the user's default locale, so some non-western (in support cases, mostly Chinese, one Korean case), characters are treated as 'illegal', which results in an HTTP protocol violation, i.e. 502 Bad Gateway error in the browser, 400 internally.
If using Confluence 6.0.2 or greater, create a new file in the Confluence home directory called synchrony-args.properties and add the following:
Restart Confluence. You should now get the red loading banner for collaborative editing and see 502 Gateway errors in the console
Collaborative editing works as expected.
In the HAR files collected we see
You can test that Synchrony can be polled with
and returns (note the date)
(Upgrade to 6.0.2+ if not already) Override the default locale for Synchrony
|Comment by Yuriy Porokhnyavyy [ 30/Dec/2016 ]|
6.0.3 the same
|Comment by Rob Biggs [ 03/Jan/2017 ]|
Seeing the same behavior after an update to 6.0.3 on Linux. Setting synchrony.proxy.enabled to false did not fix the issue. We are using an apache proxy. Previous versions of Confluence did not have issue.
|Comment by James Richards [ 03/Jan/2017 ]|
Hello Rob Biggs,
This bug is specifically for Windows without a reverse proxy. Are you seeing the 502 Bad Gateway error in the network tools tab of the browser when using a Linux server?
Either way, can you open a ticket with support at https://support.atlassian.com/ and attach
|Comment by James Richards [ 11/Jan/2017 ]|
Since you posted your comment we're done a lot more investigation and are now confident that the root cause for this issue is specifically for users with Chinese language environment (Windows/Linux and with or without reverse proxy). The symptoms however can have many causes. So, if you haven't already you can test if you have this issue or submit a support request and we can investigate further.
|Comment by Minh Tran [ 07/Feb/2017 ]|