nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIra taking up lot of memory

Rahul Aich [Nagra]

Hi All

I have got Windows server 2003 hosting my jira installation 5.0.

My problem is before i start up jira (as a service) the task manager shows 2.8 GB available memory however the moment i start-up the jira the available memory drops from 2.8 GB to 200 MB.

I am not sure y this is happening.

I have explicitly allocated a memory of 1 GB for this jira installation (using commands as mentioned in jira documentation for increasing jira memory)

I only have four plugins installed; jira charting plugin, jira misc workflow extensions, greenhopper and jira suite utilities.

Any idea what is causing this drastic drop in memory. It is often resulting in the jira abruptly shutting down due to memory running out.

Rahul

Accepted answers

unknown

Java apps have many memory pools, you have probably allocated 'one' of them to 1GB, there are others, though stretching that to another 1.2GB is a bit much. Where/what is your database (same box)?

If you monitor heap usage with JConsole you can track memory usage. If you eventually run into an OutOfMemory exception, that sounds like a memory leak from a plugin.

Monitoring your memory usage, combined with potentially disabling one plugin at a time is likely the best way to locate the cause.

All comments

unknown

Java apps have many memory pools, you have probably allocated 'one' of them to 1GB, there are others, though stretching that to another 1.2GB is a bit much. Where/what is your database (same box)?

If you monitor heap usage with JConsole you can track memory usage. If you eventually run into an OutOfMemory exception, that sounds like a memory leak from a plugin.

Monitoring your memory usage, combined with potentially disabling one plugin at a time is likely the best way to locate the cause.

Max Blackmer

I would also suggest looking at Concurrent Mark-Sweep (CMS) Garbage Collector with incremental mode to be better tuned for web applications. See more Details on my comment in https://answers.atlassian.com/questions/22592/is-your-jira-instance-growing-above-200-000-issues

Rahul Aich [Nagra]

Thanks Andy. I only observed this on test instance not on production. But the steps you mentioned is the right way to approach the problem

Rahul

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

memory