Confluence failing DB collation and character set Health check

porrittg January 22, 2020

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?

9 answers

1 accepted

2 votes
Answer accepted
Andrew Preece January 23, 2020

Version 1.23.2 appears to have resolved this issue.

Marion Creutzburg January 23, 2020

I have also upgraded to version 1.23.2 and it seems like the issue is solved.

porrittg January 24, 2020

Have upgraded and issue is resolved.  Thanks everyone

2 votes
Anna Henke January 23, 2020

A defect already exists in the Atlassian Jira: https://jira.atlassian.com/browse/CONFSERVER-59375 .

1 vote
Marion Creutzburg January 22, 2020

It is a bug, after downgrading to 1.21.2 the messages are went away.

1 vote
Frank Krüger January 22, 2020

Same here, Confluence 7.2.0 on Debian 8 with MySQL 5.6.47.

1 vote
Deleted user January 22, 2020

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.

0 votes
frs24 FRS24 January 24, 2020

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!

0 votes
Dan Fry January 23, 2020

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!

0 votes
porrittg January 23, 2020

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.

0 votes
Chuck Solie January 22, 2020

I downgraded

Atlassian Troubleshooting and Support Tools
to: 1.21.1
from: 1.23.1

 

and the messages went away, so possibly a bug?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events