The following plugins are required by JIRA, but have not been started:
Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)
JIRA Projects Plugin (com.atlassian.jira.jira-projects-pl ugin)
Atlassian Navigation Links Plugin (com.atlassian.plugins.atlassian-nav -links-plu gin)
Atlassian JIRA - Plugins - Issue Search (com.atlassian.jira.jira-issue-nav-p lugin)
Atlassian JIRA - Plugins - Quick Edit Plugin (com.atlassian.jira.jira-quick-edit- plugin)
JIRA Project Config Plugin (com.atlassian.jira.jira-project-con fig-plugin )
Atlassian JIRA - Plugins - REST Plugin (com.atlassian.jira.rest)
Opensocial Plugin (com.atlassian.gadgets.opensocial)
Embedded Gadgets Plugin (com.atlassian.gadgets.embedded)
RPC JIRA Plugin (com.atlassian.jira.ext.rpc)
Gadget Directory Plugin (com.atlassian.gadgets.directory)
Gadget Dashboard Plugin (com.atlassian.gadgets.dashboard)
#atlassian-jira-6.4.2-standalone/bin/stop-jira.sh
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 268435456 bytes for committing r eserved memory.
# An error report file with more information is saved as:
# /mnt/32GbUsb/hs_err_pid30738.log
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
From novice to tech pro — start learning today.
You may need to look into VM limits for java runtime to match the reality on a Pi but first kill off all unneeded stuff.
Pi's have 1GB of memory..., and allas using SWAP space will not help a lot, as the access paths to any external device is over one shared USB bus.
A Pi effectively comes with one path for MMC, one path for USB (including the Ethernet, which uses USB).
A PI 3 also has a private path for the built-in wireless.
On a PI 3B the fastest option might be swapping across a wireless NFS connection.
But if you need swapping then better look for a slightly larger memory system like a pine64 which can have 2GB