Tomcat server getting crashed due to out of memory

[Former Member]

We have a distributed BOXI environment. Our web server (Tomcat 5.5) is hosted on a Linux box and BOXI 3.1 SP3 application is hosted on Windows server 2008. The web server configuration details are as below. Web server (x86_64 GNU/Linux) CPU (1) - Intel(R) Xeon(R) CPU E7450  @ 2.40GHz Total Physical Memory - 1.83 GB Total Java Heap Memory - 1 GB The allocated total Java heap memory is 1 GB and the default garbage collector (Serial collector) is used. We are carrying out performance testing for this environment with with 15 users and 20 mins of steady state. The problem we are facing is when the testing is carried out the tenured heap memory is getting filled up in the middle and not freed by the major collection. This results in 404 error, while opening report in Infoview. Also the tomcat service crashes after sometime with out of memory error. We are not sure whether the existing memory sizing is correct. So please help us in getting this issue resolved. Thanks.

[Former Member]

Are you testing any PM dashboards which are based on xcelsius?

[Former Member]

No. We are testing Web Intelligence reports. Also these reports are simple ones without any graphs or dashboard in it.

[Former Member]

Hi Neeraj

        I am facing the same issue, I have  clustered environment mix of Windows and Solaris.  Physical memory is sufficient.  I´ve performed different actions so far, the major change I did was upgrade to JDK 64 bits and Tomcat6 to be able to allocate more memory, after that the issue is still the same, when the failure occurs my tomcat nodes are hanging out and I have to kill and restart them manually.   I am in XI 3.1 SP2, SAP recommended me to move to SP5 however the upgrade in my unix environment did not work.  

        My environment is large and I use Webi and Xcelsius Dashboards, I read the KB 1637342, I have not tried -Xint option, I will check if it is the same in tomcat6 and I will give it a try.

        I´ve been dealing with this error for a long time, is getting worse every day, after all the research done I suspect the only way to get rid of crashes is to identify the reports/queries which are breaking down the tomcat.  ( In your case you said your reports are simple, so maybe you have to do SP upgrade).  Now I am working to set up RSC as per SAP recommendation to check if with that tool help so identify culprit objects due to Auditing reports are not enough in my case.

        Have you escalated to SAP, I suggest you do it.

http://scn.sap.com/community/bi-platform/remote-supportability/blog/2011/08/17/web-intelligence-memo...

Cheers!

Carla

[Former Member]

Hi Kirshna,

       I have the same problem as Neeraj, and I use Xcelsius, Any suggestion from your end?

        Thx in advance

Carla.

[Former Member]

Hello Sahni,

I did a quick search on the SAP Xsaerch and found the following KBA: 1637342 - Tomcat hangs or crashes: Exception in thread "CompilerThread1" java.lang.OutOfMemoryError

This is caused mainly by a lack of memory on the Java Virtual Machine, the resolutions consists on editing the env.sh under the Instal Dir/Bobje, just follow the instructions described in the above mentionned KBA.

Regards,

Malek Jebari.

[Former Member]

Hi Malek, Thanks for your response.

I have changed settings as per the above mentioned SAP note, but still the issue persist.

[denis_konovalov]

What are the details of your testing ?

If your Linux box has only 1.8gb memory and tomcat is allocating 1gb of that, this leaves Linux itself only 800K or so....
Depending on the type of OutOfMemory errors tomcat is reporting, you might need to add more memory for OS...

Depending on the type of testing/load you're placing - you might need to increase Tomcat memory or use more agressive GC.

If you're using Webi - you might want to upgrade to FP3.7 or later as it addresses some known memory leaks and session problems.

[Former Member]

Hi, Thanks for your response.

Actually the problem is the tomcat server is now not crashing, but it is not able to free up tenured memory whe it gets filled up. The major collection happens when it gets full, but the collection is not freeing up memory when the testing is going on. But the tenured memory gets freed up after 5-10 mins, once the testing is done.

We are not sure why the tenured memory is not getting freed during major collection when testing is going on. Please advise.

[Former Member]

This behaviour results in 404 error while loading report in Infoview