Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

meminfo

```

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

```

cpuinfo

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

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
TAGS
Community showcase
Published in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

118 views 7 9
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you