Andy,
Yes, that is 4GB... just a little stressed.
I did a 'find' for all 'hs_err*.pid' files and turned up nothing, no files
were found.
I am using catalina.sh to start Tomcat and I had always assumed that the
java JVM was started in that process somewhere. I apologize for my
ignorance here but I don't see any java processes other than Tomcat and
Visual JVM (using ps -ef.) I do have a little java listener also running
that serves some data to client applets. Neither the little listener nor
Visual JVM went down when Tomcat stopped.
Tomcat is in /usr/local/tomcat (bin, conf, etc.) Java is in usr/local/java.
Is the 'cwd of the java process' the directory where the application
(Tomcat) is running or the bin directory of java? (I don't see anything in
any of those areas that looks odd or informative.)
How can I tell if the JVM is or is not running as a daemon?
TIA,
Carl
----- Original Message -----
From: "Andy Wang" <aw...@ptc.com>
To: <users@tomcat.apache.org>
Sent: Monday, January 11, 2010 6:42 PM
Subject: Re: JVM goes away
I assume $GB means 4GB :)
With that kind of memory use it doesn't sound entirely like the OOM
killer. Have you looked around the filesystem for hs_err[pid].pid
files? This usually is written to the cwd of the java process. That
might give you ideas if it's a native crash. If so, it'll have the java
stack, and other native information that might shed some light.
Otherwise, if the Tomcat JVM isn't running as a daemon, is it nohup'ed?
Andy
On 01/11/2010 05:33 PM, Carl wrote:
Peter and Andy,
Thanks for your quick responses.
Memory: Physical - $GB
Used - 2.4GB to 3.0 GB (according to top... have never
seen it above 3GB)
Swap - 19GB, none ever used (or, at least I have never
seen any used.)
The above are all from top.
The 2.4GB is after the JVM just crashed (after running less than an
hour after having run for five days with nary a blip) and I just
restarted Tomcat (customers are running right now) so it is a little
higher than normal because it has perhaps .5GB+ unrecovered from the
point at which the JVM crashed.
I checked dmsg but saw nothing that looked out of the ordinary.
I will cut back on the heap and permgen tonight (gonna be a long one.)
Any ideas are welcome.
Thanks,
Carl
----- Original Message ----- From: "Peter Crowther"
<peter.crowt...@melandra.com>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Monday, January 11, 2010 6:06 PM
Subject: Re: JVM goes away
2010/1/11 Carl <c...@etrak-plus.com>:
This is a new server, a Dell T110 with a Xeon 3440 processor and 4GB
memory. I have turned off both the turbo mode and hyperthreading.
The environment:
64 bit Slackware Linux
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode)
Tomcat: apache-tomcat-6.0.20
JAVA_OPTS="-Xms2400m -Xmx2400m -XX:PermSize=512m -XX:MaxPermSize=512m"
I have watched observed the memory usage and general performance with
Java VisualVM and have seen nothing strange. GC seems to be
performing well and the memory rarely gets anywhere near the max.
The server runs well, idling along at 2-5% load, serving jsp's, etc.
at a reasonable speed. Without warning and with no tracks in any log
(Tomcat or system) or to the console, the JVM will just go away,
disappear. Sometimes, the system will run for a week, sometimes for
only several hours. Initially, I thought the problem was the turbo or
hyperthreading but, no, the problem persists.
When the JVM goes away, the memory that it held is still being held
(as seen from top) but it is nowhere near the machine physical memory.
The application has been running on an older server (Dell 600SC, 32
bit Slackware, 2GB memory) for several years and, while the
application will throw exceptions now and then, it never crashed the
JVM. This leads me to believe the problem has something to do with
the 64 bit JVM but, with errors, I can't be certain and don't know
what I can do about it except go back to 32 bit.
I plan to reinstall Java tonight but, it would seem if the JVM were
corrupted, it simply would not run.
Any ideas are welcome.
I'm with Andy: the Linux OOM killer would show those symptoms. With
those settings, you're not leaving a lot of memory for the OS. How
much swap do you have, and does the same thing happen if you reduce
the Java heap and permgen space?
- Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
