History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-3157
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Robin Shen
Reporter: Mike Cordeiro
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Database Upgrade failed but Configuration still Upgraded

Created: 26/Mar/18 01:00 PM   Updated: 28/Jan/19 01:29 PM
Component/s: None
Affects Version/s: 8.0.0
Fix Version/s: 8.0.35

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: Windows Server/SQL Server

 Description  « Hide
We had an issue when upgrading to 8.0.0 where the upgrade of the database failed, but the configuration was still upgraded leaving QB in an invalid state.

The first time we tried to run the upgrade it turned out that while we had updated the wrapper.conf in our installation to point the java command to a JDK 8, the upgrade command uses whatever the default java command is on the machine.. A couple of our internally written plugins were written against JDK 8, and the upgrade ran with JDK 7, so it threw an UnsupportedClassVersionError. Unfortunately, the upgrade continued and did not report failure. When I tried to start QB after the upgrade, I received an error that the database was at version 94 and needed to be at version 98. Thankfully the upgrade scripts take a backup of the configuration and I was able to roll back.

 All   Comments   Work Log   Change History      Sort Order:
Robin Shen [27/Mar/18 03:30 AM]
Make sure to edit wrapper.conf of QB8 to point to JDK8, as upgrade command is running from QB8's installation directory and will be using QB8's configured JDK.

Robin Shen [27/Mar/18 04:42 AM]
We will improve QB to abort the upgrade procedure in case such issue is encountered