Issue upgrading Jira from 5.2.9 to 6.1.4

[Systems Group]

Following the instructions at https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA+Using+a+Rapid+Upgrade+Method

when executing the atlassian-jira-6.1.4.bin file:

1) I choose Upgrade existing Jira installation

2) It finds the correct Jira install directory

3) I type 'y' to backup Jira Home Directory

However, when "checking for local modifications" I get the following error:

List of modifications made within JIRA directories.

An error occurred:

java.lang.OutOfMemoryError: Java heap space

Error log: /usr/local/atlassian/install4jError3236897897978096157.log

java.lang.OutOfMemoryError: Java heap space

at java.util.Arrays.copyOf(Unknown Source)

at java.lang.AbstractStringBuilder.expandCapacity(Unknown Source)

at java.lang.AbstractStringBuilder.ensureCapacityInternal(Unknown Source)

at java.lang.AbstractStringBuilder.append(Unknown Source)

at java.lang.StringBuffer.append(Unknown Source)

at com.install4j.runtime.util.StringUtil.replaceVariable(Unknown Source)

at com.install4j.runtime.installer.InstallerVariables.replaceVariables(Unknown Source)

at com.install4j.runtime.installer.frontend.components.HtmlDisplay.getOrLoadText(Unknown Source)

at com.install4j.runtime.installer.frontend.components.HtmlDisplay.handleConsole(Unknown Source)

at com.install4j.runtime.beans.screens.InfoScreen.handleConsole(Unknown Source)

at com.install4j.runtime.installer.frontend.headless.ConsoleScreenExecutor.handleScreen(Unknown Source)

at com.install4j.runtime.installer.frontend.headless.AbstractHeadlessScreenExecutor.execute(Unknown Source)

at com.install4j.runtime.installer.controller.Controller$1.run(Unknown Source)

at java.awt.event.InvocationEvent.dispatch(Unknown Source)

at java.awt.EventQueue.dispatchEventImpl(Unknown Source)

at java.awt.EventQueue.access$200(Unknown Source)

at java.awt.EventQueue$3.run(Unknown Source)

at java.awt.EventQueue$3.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.run(Unknown Source)

Finishing installation ...

[Systems Group]

Before I attempt a manual upgrade, would it be better to try to upgrade to an intermediate version of Jira (such as 6.0.1)? Could this be the problem?

Any help would be greatly appreciated. Thanks!

[Systems Group]

Since it appears no one has encountered this, I will try using an alternate method of upgrading.

I was considering just doing a manual upgrade which would involve a fresh install to a new jira install directory pointed to a copy of the original jira home directory. I would connect the new Jira to an empty external database and then do a restore from an XML backup of the current Jira.

Does anybody see a downside to this beside that manual migration of the old Jira configuration?

[RambanamP]

you need to increase the heap memory, check this doc

https://confluence.atlassian.com/display/CONFKB/Confluence+Out+of+Memory+Java+Heap+Space

https://confluence.atlassian.com/display/CONFKB/How+to+Fix+Out+of+Memory+Errors+by+Increasing+Available+Memory

[Systems Group]

I have increased the heap memory using the Jira specific directions directions found here: https://confluence.atlassian.com/display/JIRA/Increasing+JIRA+Memory

I went up as high as 2GB, which would seem unnecessary with such a small install. However, this does not fix my problem. I'm still unable to upgrade, and am getting the same error at the same point in the process.

[Zul NS _Atlassian_]

What is your database stats and machine specs? Are you on x64 OS and JIRA installer?

[Systems Group]

Machine Specs:

Virtual Machine

4 GB RAM

CentOS (64 bit)

Dual Core Intel(R) Xeon(R) CPU E5-2667 0 @ 2.90GHz

Specifically what database stats do you need?

I don't think this is a resource issue as Jira has been working quite snappy and without a hitch for some time now. I've done upgrades before and never had this issue.