ERR_CONNECTION_RESET after Update to 6.14
Asked by Michael Wagner:

Dear all,

today we did an update to 6.14.0_x64

Update ran without any problems/errors ... Confluence Service ist starting, but browser shows ERR_CONNECTION_RESET ... no page is beeing displayed.

Details:

- running on h2db (yes, we're planing to switch)

- reinstalled windows service correctly

- JRE 1.8 installed on machine

- JRE System Variable is set

- Machine is Windows Server 2012

- Firewall turned off

New Information ... we're getting the following error on Login-Screen (Webpage)

Unable to start up Confluence. Fatal error during startup sequence: confluence.lifecycle.core:mananagedjobs (Start and stop the Managed Scheduled Jobs)

JDBC exception on Hibernate data access: SQLException for SQL \[n/a\]; SQL state \[HY000\]; error code \[50000\]; could not extract ResultSet; nested exception is org.hibernate.exception.GenericJDBCException: could not extract ResultSet

Any Ideas?

Best,

Mike

Details:


Answers:
author: Michael Wagner
body: ...in the absence of any response I had to do it on my own.

Finally I got Confluence Original Version 6.5 up and running.

2 things about it:

++1) this seems to be a known bug in H2DB++ ... check <http://h2-database.66688.n3.nabble.com/TimeNanos-out-of-range-when-using-different-version-of-jar-No-check-when-DB-upgraded-td4033636.html>

**YOU SHOULD WARN ABOUT THIS BUG DURING UPDATE**

2) I want to migrate the Database to MySQL -\> please advise about the procedure doing it on the original machine (manually creating the mysql-db, importing the db-content, changing the db-location in confluence, etc.)

An please're so kind don't telling me to setup a fresh on a new location, import the site, etc. ... this isn't a common way to do it on enterprise-like appliactions like confluence ... there has to be a possibility to change the database.

Best,

Mike

comments: author: Shannon S
body: Mike,

Happy to hear you were able to work around the issue! Unfortunately your message had come in on Saturday after I had gone home for the weekend, so I wasn't able to see it until this morning.

I wasn't aware of the bug with the H2DB, but thankfully it's not an issue too many users should run into with Confluence since it's only supported for the evaluation period, which would not generally require upgrade. The evaluation period is 30 days, and any versions that are released within 30 days of each other tend to be more or less the same features. Any staging of upgrades should be completed with the exact database version you intend to use in your production upgrade.

I've submitted the request below, to make it more clear for users that upgrade is not supported when using the embedded database, as this is outside of simply evaluating Confluence.

* [CONFSERVER-57849](https://jira.atlassian.com/browse/CONFSERVER-57849)

On this request I have also referred to the example you shared with me, so we can avoid the same happening to users in the future.

To [migrate the database](https://confluence.atlassian.com/doc/migrating-to-another-database-148867.html?_ga=2.67010983.800021067.1549283132-1735250289.1546433624), you want to use the instructions I sent you earlier. If you have a fresh MySQL database, you need to connect it to a fresh Confluence installation so Confluence can build the required tables. Importing the XML file into this fresh installation is what brings your data over.

I can't think of a way to avoid setting up a new Confluence instance, but you could try the following:

1. Follow the steps in the linked article to setup a fresh Confluence installation.
2. Create an XML backup of your existing instance, and stop Confluence.
3. Import your XML file on the new instance.
4. Stop the new Confluence instance.
5. [Update the database connection parameters](https://confluence.atlassian.com/confkb/how-to-find-confluence-s-database-connection-parameters-779172320.html) in the existing instance to point to the new database.
6. Start Confluence on the existing installation.

I don't believe this would save you much time in the end, but you're welcome to try it if you would rather do that than start a new instance. Please note that this method isn't supported, so if it fails in the end, I would encourage you to try the supported method.

Regards,

Shannon


author: Shannon S
body: Mike,

To resolve this error, you'll need to perform the migration now from off of the embedded database to a [supported database](https://confluence.atlassian.com/doc/supported-platforms-207488198.html).

You can use the steps from the below article:

* [Migrating to Another Database](https://confluence.atlassian.com/doc/migrating-to-another-database-148867.html)

Please review the article and do let us know if you have any questions or any roadblocks.

Regards,

Shannon

comments: author: Michael Wagner
body: Dear Shannon,

yes, we'll do the migration - but we want to do it plannend (next week, to mysql).

At first we need to get it up and running as it is, we'll need the service this weekend.

How can I recover the service using this database?  
I'll migrate it afterwards...

Best,

Mike


author: Michael Wagner
body: I cann't believe that Confluence is stop working after update using embedded db - even for test/dev not a good idea ...

please advise


author: Shannon S
body: Michael,

This is a very common problem that occurs when upgrading a Confluence instance with the embedded H2 database. In each instance that I saw this error, a migration to a supported database resolves the issue. When staging an upgrade or migration, you want to make sure to test with the exact version of database that you use on your production instance. This will ensure your tests are fully accurate.

As you are already aware, the H2 database is only supported during the evaluation period, which is the first 30 days. As your instance license is outside of the evaluation period, I would recommend migrating immediately in order to recover your data.

I apologize, but I am not aware of any further resolutions, and I have consulted with the rest of the Confluence server team, and they confirm the same.

Thank you for your understanding.

Shannon


author: Michael Wagner
body: Hello there,

**Let me clarify** ... Confluence was up and running till the update.  
If you guys're knowing about issues like that (after Update -\> no way to get it up an running again) ... you should create A BIG RED SPLASH SCREEN or something like that.  
Supported or not ... this isn't a good way to do it. You made my day.

**Database Decision**   
The actual MySQL Community Server is 8.0.15  
Regarding to Supported Platforms this version isn't supported, so I'll install MySQL Community Server 5.7.25 ... hope this will be OK???

**Database Setup**   
all Documents are talking about "do a fresh setup ... confluence installer will create the database"  
Whats about manually creating the database -\> are there "database create scripts"???

**Migrating / Site export**   
all Documents are talking about "General Configuration \> Backup \& Restore" ... as I told you ... confluence isn't running ...  
(http://localhost:8090/confluence/admin/backup.action ... isn't working as well)  
How to manually export the content, configuration, the full installation

**Installation**   
all Documents are talking about "install confluence to a new location"  
I don't want to do this.  
I'll migrate embedded database to mysql instance - ok ... but I want to do it on the same machine confluence is actually installed.  
Please advise steps to do it like this.

Really unhappy, I'll do, but please advise.

Best,  
Mike


author: Michael Wagner
body: Hello there,

any suggestion about that?  
I've to fix it quick!

Best,

Mike


Tags: confluence-server

server