Chuck,
Darn, I thought we were onto something here but, as you suspected, the line
contains a lot of parameters and was truncated. So, now, I think we know
the JVM is seg faulting, we just don't know where or why. I'm guessing we
have to somehow get a stack trace at the point of failure... any idea how I
can get one? Or, is there a better way?
Thanks,
Carl
----- Original Message -----
From: "Caldarale, Charles R" <chuck.caldar...@unisys.com>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Friday, February 12, 2010 4:52 PM
Subject: RE: Tomcat dies suddenly
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly
How does this line:
`/usr/local/java/bin/java -
Djava.util.logging.config.file=/usr/local/tomcat/conf'
know that it is supposed to use the logging.properties
file if that is the problem?
It doesn't know. The command line parameter should be:
-Djava.util.logging.config.file=/usr/local/tomcat/conf/logging.properties
Perhaps the display is just a truncation, since there should be several
additional command line parameters beyond that one.
Use JConsole to see if the full set of properties are present when Tomcat
is running normally.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
