Hi guys,
I have a little problem here with tomcat heap size. This issue occures after update from 4.0 SP6.5 to 4.1 SP2 (tomcat6 to tomcat7). I am restarting tomcat every evening to clean servers memory. I will describe situation of this morning. Yesterday at 7 PM i restarted tomcat. Now at 10 AM, tomcat service is consuming about 5.5 GB of memory and it is still growing. Here is screenshot of VMMap tool.
When i look at xxx.com:8080/manager/status i can see these values for JVM: Free memory: 36.55 MB Total memory: 216.93 MB Max memory: 1820.50 MB. Its realy wierd.
Tomcat settings is default:
-Djava.library.path=xxx
-Dcatalina.base=xxx
-Dcatalina.home=xxx
-Djava.endorsed.dirs=xxx
-Dbobj.enterprise.home=xxx
-Xrs
-XX:MaxPermSize=384M
-Dbusinessobjects.olap.bin=
-Dbusinessobjects.olap.stylesheets=
-Djava.awt.headless=true
-Djava.security.auth.login.config=xxx
-Djava.security.krb5.conf=xxx
-XX:+HeapDumpOnOutOfMemoryError
-Xloggc:xxx
-XX:+PrintGCDetails
-XX:+UseParallelOldGC
and maximum memory pool 2048m and thread stack size 1024k.
I thing that issue might be caused by a lot of Qaaws requests. We are running dashboards on 10 TVs and every TV produce about 5 qaaws requests/minute under same enterprise account. According to xxx.com:8080/manager/status, QaaWS Servlet has performed 20000 requests in last 15 hours. There are no qaaws requests and heap size is still on our test server.
Do you have any idea how to get deeper and see what's going on?
Tomas