The health check in our self hosted Confluence installation is fail for the DB collation and character set. Both have the same result message:
Exception during health check invocation java.lang.RuntimeException: java.sql.SQLException: You can't operate on a closed ResultSet!!!
I've trawled the web but can't seem to find anything on this.
I should add we're running on Windows with MySQL 5.7 DB
Any ideas?
Version 1.23.2 appears to have resolved this issue.
I have also upgraded to version 1.23.2 and it seems like the issue is solved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is a bug, after downgrading to 1.21.2 the messages are went away.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here, Confluence 7.2.0 on Debian 8 with MySQL 5.6.47.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can confirm same behaviour on Linux as well also with MySQL 5.7 and Confluence 7.2.0 and 7.2.1. No apparent errors in the logs.
Also on another install which is still v 7.1.0 the same error.
And of course collation and character set is set according to documentation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, there's an update for the "troubleshooting and support tools" app in Confluence - after the upgrade to v1.23.2 the issue was gone!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are having the same issue since upgrading the Atlassian Troubleshooting and Support Tools plugin last night, the Database and Server are both set correctly to UTF-8. I have raised a ticket to Atlassian already so hopefully they push out a patch or fix for this if it's a bug!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the replies. It's good to know that it's not just something with our installation. I couldn't find anything on google so I assumed it was an issue with our setup.
As everything seems to be working okay I'll leave things for now and see if they push an update sometime soon. if they don't, I'll consider downgrading.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I downgraded
Atlassian Troubleshooting and Support Tools
to: 1.21.1
from: 1.23.1
and the messages went away, so possibly a bug?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.