JIRA stops working on making changes to setenv.bat

Saneth Kumar
Contributor
May 17, 2012

I installed a new instance of JIRA and tried to restore it with an XML backup. However, it gave me the *java.lang.outofmemoryerror gc overhead limit exceeded* error. I tried making changes to *setenv.bat* as suggested in the documentation - GC Overhead Limit Exceeded|http://confluence.atlassian.com/display/JIRAKB/GC+Overhead+Limit+Exceeded and Increasing JIRA Memory|http://confluence.atlassian.com/display/JIRA/Increasing+JIRA+Memory . However, when i make changes to this file and try to start JIRA, it crashes within a few seconds and leaves no logs.

2 answers

1 accepted

0 votes
Answer accepted
Saneth Kumar
Contributor
May 25, 2012

I realized that there was a problem with regarding our RAM allocation. We're using 8GB of RAM on a 32-bit operating system, and 32-bit operating systems can only utilize 4GB of RAM. Therefore, when I made changes to setenv.bat it conflicted with our RAM and caused JIRA to crash.

1 vote
Colin Goudie
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 17, 2012

Can you take a look at the catalina.out logs? These should be in the JIRA installation directory (under logs) rather than the JIRA home directory (where the atlassian-jira.log file is)

Saneth Kumar
Contributor
May 25, 2012

Hi Colin,

Thanks for the reply.

Saneth

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events