Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira Server Software GC Allocation Failure for Migration Assistant Installation

I tried to install Jira Cloud Migration Assistant on my On Premise Jira Server

but installation fails with (logs):

Java HotSpot(TM) 64-Bit Server VM (25.181-b13) for linux-amd64 JRE (1.8.0_181-b13), built on Jul  7 2018 00:56:38 by "java_re" with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)

Memory: 4k page, physical 4194304k(1880304k free), swap 524288k(92048k free)

CommandLine flags: -XX:GCLogFileSize=20971520 -XX:InitialCodeCacheSize=33554432 -XX:InitialHeapSize=402653184 -XX:MaxHeapSize=805306368 -XX:NumberOfGCLogFiles=5 -XX:-OmitStackTraceInFastThrow -XX:+PrintGC -XX:+PrintGCCause -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:ReservedCodeCacheSize=536870912 -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseGCLogFileRotation -XX:+UseParallelGC

2023-03-28T16:01:39.476-0400: 1.251: [GC (Allocation Failure) [PSYoungGen: 98304K->15213K(114688K)] 98304K->15301K(376832K), 0.0214553 secs] [Times: user=0.06 sys=0.01, real=0.02 secs]

2023-03-28T16:01:39.818-0400: 1.594: [GC (Allocation Failure) [PSYoungGen: 113517K->16378K(212992K)] 113605K->16922K(475136K), 0.0153823 secs] [Times: user=0.04 sys=0.01, real=0.01 secs]

2023-03-28T16:01:40.252-0400: 2.027: [GC (Allocation Failure) [PSYoungGen: 212986K->16364K(212992K)] 213530K->19915K(475136K), 0.0202696 secs] [Times: user=0.06 sys=0.01, real=0.02 secs]

2023-03-28T16:01:40.567-0400: 2.343: [GC (Allocation Failure) [PSYoungGen: 212972K->16378K(245760K)] 216523K->23362K(507904K), 0.0190884 secs] [Times: user=0.05 sys=0.01, real=0.02 secs]

2023-03-28T16:01:40.966-0400: 2.741: [GC (Allocation Failure) [PSYoungGen: 245754K->16382K(245760K)] 252738K->27667K(507904K), 0.0210301 secs] [Times: user=0.07 sys=0.01, real=0.02 secs]

2023-03-28T16:01:41.407-0400: 3.182: [GC (Allocation Failure) [PSYoungGen: 245758K->16361K(220160K)] 257043K->41456K(482304K), 0.0336480 secs] [Times: user=0.09 sys=0.01, real=0.03 secs]

1 answer

0 votes
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 31, 2023


The error you noted looks like a Garbage collection issue, Keep in mind that most of these types of errors arise because the Java heap is too big and causes an overflow during the garbage collection tasks, HOWEVER, that are a lot of different things that could be occurring so please check out the following Guides that are a good starting point for performance tuning on the instance and steps to help start narrowing down the causal factors:

But again there are a lot of varying factors that can trigger this behavior, so if you do need additional assistance digging into the logs and settings I recommend reaching out to our support portal at and sending a Support ZIP  with that request.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events