tomcat memory

[coolname]

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?

[QueueMetrics]

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

[coolname]

i will check the availiable memory

[coolname]

not the problem about available memory,any other suggestion?

[emilec]

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

[coolname]

[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)

[QueueMetrics]

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

[emilec]

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

[coolname]

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

[coolname]

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)

[emilec]

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

[coolname]

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

[QueueMetrics]

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

[coolname]

should i change another jsp container ?

[QueueMetrics]

No - memory looks aplenty.

Try and take a memory dump.