accidently launched 6.3.6 now cannot launch 6.2.6

I accidentally launched 6.3.6.  i stopped 6.3.6 and then launched 6.2.6 now getting


An error occurred performing JIRA upgrade

The data before the upgrade has been exported to /opt/atlassian/jira/prod/data/export/
2014-11-18 11:40:37error
Exception thrown during upgrade: Illegal group reference
java.lang.IllegalArgumentException: Illegal group reference
	at java.util.regex.Matcher.appendReplacement(
	at java.util.regex.Matcher.replaceFirst(
	at java.lang.String.replaceFirst(
	at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build6209.renameAllVersions(
	at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build6209.doUpgrade(
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSuccess(
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.runUpgradeTasks(
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgrade(
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(
	at com.atlassian.jira.upgrade.UpgradeLauncher.checkIfUpgradeNeeded(
	at com.atlassian.jira.upgrade.UpgradeLauncher.start(
	at com.atlassian.jira.startup.ActiveServicesLauncher.start(
	at com.atlassian.jira.startup.DefaultJiraLauncher$
	at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(
	at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(
	at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(
	at com.atlassian.jira.startup.DefaultJiraLauncher.access$100(
	at com.atlassian.jira.startup.DefaultJiraLauncher$
	at com.atlassian.jira.startup.DefaultJiraLauncher.start(
	at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(
	at org.apache.catalina.core.StandardContext.listenerStart(
	at org.apache.catalina.core.StandardContext.startInternal(
	at org.apache.catalina.util.LifecycleBase.start(
	at org.apache.catalina.core.ContainerBase$
	at org.apache.catalina.core.ContainerBase$
	at java.util.concurrent.FutureTask$Sync.innerRun(
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
	at java.util.concurrent.ThreadPoolExecutor$

1 answer

1 vote

I assume when you say you accidentally launched 6.3, it was pointed at the 6.2 database?

That means you're pretty much stuck.  6.3 will have upgraded the data to 6.3, which makes it useless to 6.2.  Your 6.2 install is now detect the version mismatch, thinking "it's older, I should upgrade" and falling over because it can't.

However, you need to establish that my guess is right first.  If it is, then you'll need to go back to the last database backup (The data can't be easily downgraded - you're looking at days or weeks of work).  But I'm really not 100% sure that is what has happened.

Chris Fuller Atlassian Team Nov 18, 2014

Nic's answer is almost correct (upvoted), but there's a little bit more going on here. 6.2 detects the version mismatch, but it does not think "it's older, I should upgrade". It in fact knows that this is a downgrade. It just doesn't realize that it isn't a supported one. Like most Atlassian products, JIRA does not test (and therefore does not support) downgrades as a general solution to the problem. The reasons for this are numerous, but the easy ones to see are that downgrade processes add a lot of complexity both to development and to test efforts, and they tend to be fragile. It's effort that seems better directed at fixing bugs and developing new features, especially when taking a backup first is much more robust strategy. However, there is one specific case where we do support a downgrade, and that is when migrating from JIRA Cloud (formerly OnDemand) to JIRA Server (formerly just "JIRA"). This process is described here: Although we probably should, we don't lock this down when we release JIRA Server, so if your older version is late enough, then JIRA assumes that a migration from Cloud is the reason for the version mismatch and attempt to downgrade the data accordingly. Your 6.2.6 was the minimum supported downgrade version when 6.3 was released, so it is (accidentally) recognized as a valid downgrade target. But there are two problems. 1) We don't maintain this. It looks like by the time 6.3.6 came around, enough changes were in to break it. 2) Even if it accidentally worked, it wouldn't be supported. So yes, Nic's advice is spot on. Take the hit and restore from a backup. Anything else is asking for additional pain.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,095 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you