OutOfMemoryError message

[Alexis Baker]

Hi,

We've received an OutOfMemoryError message, and we believe it has caused jira to crash a couple of times in the past month.

Do you know what might be causing this?

I noticed last time a reindex was required as a change was made the day before, but reindex didn't happen. Could this be a factor ?

A new add on was added a couple of months ago (TM4J), but I would have thought that it would be compatible?

We run Jira Server - Jira version v8.3.0 

Any help would be greatly appreciated.

Thanks,

Alexis

[Danyal Iqbal · Accepted solution]

I would increase the memory as a first step and pray that it does not happen again but that might not help at all.

You should open a support request with Atlassian. Nobody can help you troubleshoot OOM exception without the logs.

in the meanwhile you can check out the various known cause for OOM and theri resolution at:

https://confluence.atlassian.com/confkb/how-to-fix-out-of-memory-errors-by-increasing-available-memory-154071.html

https://confluence.atlassian.com/jirakb/jira-server-crashes-with-outofmemory-java-heap-space-error-191069.html

[Alexis Baker]

Thanks, we have also raise a support case to see if they can help to our specific case

[Colin McDermott_GLiNTECH]

Guessing someone else may find this... Follow all that Danyal Iqbal says but adding:

How long does it take Jira to crash? Java 8 tends to hold and hold memory, while Java 11 will release memory. Meaning if you find that the OOM errors occur over a week, changing your JVM to Java 11 may help as Java 11 will return memory to the OS and not just grow, and grow and grow. 

You need insight into your instance. https://github.com/javamelody/javamelody/wiki/AtlassianPlugin would be my first step if you don't have it installed already. (FYI it is very lean resource wise, I can't actually measure it's performance impact >1%)