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

Error Unable to allocate memory

Hello! We began to fall JIra ver 8.8.1. I see in logs that message

OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000a9480000, 245891072, 0) failed; error='Невозможно выделить память' (errno=12)
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 245891072 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmp/hs_err_pid8686.log



MemTotal: 4039484 kB
MemFree: 111196 kB
MemAvailable: 45944 kB
Buffers: 13700 kB
Cached: 91640 kB
SwapCached: 4536 kB
Active: 3127540 kB
Inactive: 638788 kB



2 core



processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 6
model name : Common KVM processor
stepping : 1
microcode : 0x1
cpu MHz : 3292.526
cache size : 16384 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc nopl xtopology cpuid pni cx16 x2apic hypervisor lahf_lm cpuid_fault pti
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass
bogomips : 6585.05
clflush size : 64
cache_alignment : 128
address sizes : 40 bits physical, 48 bits virtual
power management:



Thank you

1 answer

1 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 18, 2020

You have set your maximum "heap" size for the java virtual machine higher than your server actually has the memory for.

You should set your maximum heap to at least 1Gb lower than the physical memory of the server (unless you're using an optimised or lightweight operating system, you should be allowing at least 1Gb for most OS's.  Probably 2Gb if you're using something bloated or with poor resource allocation, like Windows)

Thank you

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events