crash of diablo-amd64 in production system
nckjagger at yahoo.com
Thu Jul 5 09:33:41 UTC 2007
I have had a crash of the diablo JVM on an amd64 production server.
The JVM is running 10 web apps in Tomcat.
The GC log was overwritten at the (rush) restart of the JVM. Is it possible to prevent this?
I have observed that the free memory reported by the JVM in Tomcat manager decreases gradually over time.
What also seems strange to me: in the GC logs I collected there had not been a full GC over a period of two weeks. Only 'scavenges' are performed. I am using HP Jmeter to analyze the GC logs.
These are my JVM options. Can you comment on them?
jvm_args: -Xms2048m -Xmx2048m -XX:MaxPermSize=512m -verbose:gc -XX:+PrintTenuringDistribution -XX:+PrintHeapAtGC -XX:+PrintGCTimeStamps -Xloggc:/var/log/tomcat/gc.log -Djava.endorsed.dirs= -Dcatalina.base=/usr/local/tomcat5.5 -Dcatalina.home=/usr/local/tomcat5.5 -Djava.io.tmpdir=/usr/local/tomcat5.5/temp
The server has 4GB of memory and is mainly running Tomcat5.5.20 on diablo-1.5.0-b01 and Apache2.2.3.
I have the hs_err crash log attached. I would be very grateful if someone can point to a possible cause of the problem.
Get the Yahoo! toolbar and be alerted to new email wherever you're surfing.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 29445 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-java/attachments/20070705/a711f5d7/utf-8qhs5Ferr5Fpid28387.obj
More information about the freebsd-java