ZEE fails to launch : java.lang.OutOfMemoryError for Zephyr Enterprise installed on Linux OS

February 26, 2015

If anyone finds OutOfMemoryError or lack of memory in the Java heap space due to which ZEE fails to launch.

java.lang.OutOfMemoryError: Java heap space
2015-02-25 08:05:00,407 ERROR [scheduler_Worker-6] ErrorLogger.schedulerError(2166) | Job (etlGroup.DefectTrendJob threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.OutOfMemoryError: Java heap space]
at org.quartz.core.JobRunShell.run(JobRunShell.java:210)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546)
Caused by: java.lang.OutOfMemoryError: Java heap space

Here are the following steps that one should follow

1.Please verify the memory setting in the following file


For ex:The entry below in this file shows that the memory is 768m which can be low and the memory needs to be increased

export JAVA_OPTS="-server -Xms128m -Xmx768m -XX:MaxPermSize=256m -Dorg.terracotta.quartz.skipUpdateCheck=true"

2.To decide to how much the memory should be increased ,please do contact Zephyr Support with the above file and also the result set by running the following queries based on which we can decide what would the apt increase in memory be favorable.Its dependent on the number of project,releases,test cases,test schedule and user.This is always advisable to contact the support team for confirming about the memory value

SELECT COUNT(1) project_count FROM project;

SELECT COUNT(1) releases_count FROM releases; 

SELECT COUNT(1) testcase_count FROM testcase;

SELECT COUNT(1) execution_count FROM release_test_schedule;


3.Once Zephyr support receive the result set and the memory details , Zephyr internal teams decide on the next memory value to be set and communicate to the customer.

4.Make the changes in the memory values as reccomended by the support team of Zephyr in the setenv.sh file and restart the Zephyr server

5.Please verify by launching the ZEE application and logging in , which should work fine from now on.