Summary
When customer hit into an issue editing a page or saving a page, the error message that shows to the customer are "Unable to communicate with server. Saving is not possible at the moment". However, this could cause confusion to the customer as the root cause of the issue is caused by a page containing some special characters.
2018-04-20 12:44:20,074 ERROR [http-nio-8001-exec-72] [common.error.jersey.ThrowableExceptionMapper] toResponse Uncaught exception thrown by REST service: Hibernate operation: could not execute statement; uncategorized SQLException for SQL []; SQL state [HY000]; error code [1366]; Incorrect string value: '\xF0\x9F\x8F\x84</...' for column 'BODY' at row 1; nested exception is java.sql.SQLException: Incorrect string value: '\xF0\x9F\x8F\x84</...' for column 'BODY' at row 1
-- referer: https:org.springframework.jdbc.UncategorizedSQLException: Hibernate operation: could not execute statement; uncategorized SQLException for SQL []; SQL state [HY000]; error code [1366]; Incorrect string value: '\xF0\x9F\x8F\x84</...' for column 'BODY' at row 1; nested exception is java.sql.SQLException: Incorrect string value: '\xF0\x9F\x8F\x84</...' for column 'BODY' at row 1
Caused by: java.sql.SQLException: Incorrect string value: '\xF0\x9F\x8F\x84</...' for column 'BODY' at row 1
Suggestion
It will be better to have a clear error message when a page is not able to edit or save.
Hi All,
I wanted to follow up on our update above. The Confluence server development team has now completed both item 1 (Support for emoji in MySQL) and item 2 (providing meaningful error messages). We strongly encourage customers to follow the steps outlined in our documentation to migrate from UTF8 to UTF8MB4, completely resolving this issue.
If you are unable to migrate to UTF8MB4 we have added a number of meaningful error messages to Confluence to stop users attempting to add unsupported 4-byte characters. We have added these errors to:
Thanks,
Ganesh