QueueMetrics forum

QueueMetrics => Running QueueMetrics => Topic started by: coolname on February 13, 2012, 03:04:28

Title: tomcat memory
Post by: coolname on February 13, 2012, 03:04:28

(http://i.6.cn/cvbnm/10/1a/a8/75d9af02cb3ff2526c1a65aef2467398.jpg)

to fix the error,i change the  /etc/init.d/qm-tomcat6 file from "export JAVA_OPTS="-Xms2048M -Xmx2048M -server"" to ""export JAVA_OPTS="-Xms3072M -Xmx3072M -server"",but then QM can't start,does tomcat limit the memory?

Title: Re: tomcat memory
Post by: QueueMetrics on February 15, 2012, 17:09:59

No we do not, are you sure the server has enough RAM and the JVM is correct 32/64 bit for your system?

Title: Re: tomcat memory
Post by: coolname on February 16, 2012, 05:08:49

i will check the availiable memory

Title: Re: tomcat memory
Post by: coolname on February 19, 2012, 03:00:27

not the problem about available memory,any other suggestion?

Title: Re: tomcat memory
Post by: emilec on February 23, 2012, 14:25:45

what is the output of:
# cat /etc/issue
# free
# /usr/local/queuemetrics/java/bin/java -version

Title: Re: tomcat memory
Post by: coolname on February 24, 2012, 08:21:13

[root@app ~]# cat /etc/issue
CentOS release 5.6 (Final)
Kernel \r on an \m

[root@app ~]# free
             total       used       free     shared    buffers     cached
Mem:       8309008    8015628     293380          0     222688    5585336
-/+ buffers/cache:    2207604    6101404
Swap:      6291448         12    6291436
[root@app ~]# /usr/local/queuemetrics/java/bin/java
java          javac         javadoc       javah         javap         java-rmi.cgi  javaws       
[root@app ~]# /usr/local/queuemetrics/java/bin/java
java          javac         javadoc       javah         javap         java-rmi.cgi  javaws       
[root@app ~]# /usr/local/queuemetrics/java/bin/java -version
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) Server VM (build 17.1-b03, mixed mode)

Title: Re: tomcat memory
Post by: QueueMetrics on February 24, 2012, 10:26:44

You can see it from the DBTEST page of QM, select "View configuration" then "Current memory properties".

Title: Re: tomcat memory
Post by: emilec on February 24, 2012, 16:28:55

Looks to me like you have 32-bit java. Here is what I have on my 64 bit system

# /usr/local/queuemetrics/java/bin/java -version
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)

What is the output of:
# uname -a

Title: Re: tomcat memory
Post by: coolname on March 05, 2012, 03:21:03

yes 32bit
after search the google，i found itmay because of the limit of jvm , after a test of "java -XmxXXXXM -version",i found a max stable number is 2600

Title: Re: tomcat memory
Post by: coolname on March 12, 2012, 11:09:20

a test in centos 6.2 64bit, 7000M memory is ok

now report 


-- Inner Exception -- - Exception: java.lang.OutOfMemoryError - Error: - PermGen space - Stack trace: - java.lang.OutOfMemoryError: PermGen space - at java.lang.Throwable.getStackTraceElement(Native Method)

Title: Re: tomcat memory
Post by: emilec on March 13, 2012, 06:45:19

How big is the report your are drawing? Try reduce the date range.

Title: Re: tomcat memory
Post by: coolname on March 13, 2012, 06:51:04

i guess about 120000 more，but the report contains only a little items，can QM support more data analysis？

Title: Re: tomcat memory
Post by: QueueMetrics on March 13, 2012, 08:41:44

120000 calls for 7 gigs? this sounds a bit off :-)

Title: Re: tomcat memory
Post by: coolname on March 14, 2012, 02:09:22

should i change another jsp container ?

Title: Re: tomcat memory
Post by: QueueMetrics on March 22, 2012, 11:37:52

No - memory looks aplenty.

Try and take a memory dump.