Jira OOM when requesting large time sets

[Stefan Bogdan Cimpeanu]

Hello, In our Jira instance, when we request a worklog report for 1 year for a project that has 2700 issues, Jira gets totally unresponsive, and eventually we need to restart the service.

Is there a way we could: a) run those reports a separate JVM procress that we can control better or b) optimize things so we don't encounter this issues

Our Jira JVM loks like this:

/usr/java/jre1.8.0_45//bin/java -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -server -Xms3072m -Xmx3072m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -verbose:gc -Xloggc:/var/atlassian/application-data/jira/log/atlassian-jira-gc-2017-03-21_1426.log -XX:GCLogFileSize=20M -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -Dfile.encoding=utf-8 -XX:+PrintGCDateStamps -XX:-OmitStackTraceInFastThrow -Djava.endorsed.dirs=/opt/atlassian/jira/endorsed -classpath /opt/atlassian/jira/bin/bootstrap.jar:/opt/atlassian/jira/bin/tomcat-juli.jar -Dcatalina.base=/opt/atlassian/jira -Dcatalina.home=/opt/atlassian/jira -Djava.io.tmpdir=/opt/atlassian/jira/temp org.apache.catalina.startup.Bootstrap start

Thanks!

[Andriy Zhdanov]

Hi Stefan,

It's only possible to limit Maximum Period for the plugin (see Administration - Add-ons - Timesheet Configuration) or make sure Show Details is switched off (it also can be enforced with Maximum Worklogs option in Timesheet Configuration). Please see issue#169 also.

Thank you.