I was facing a problem with similar symptoms - Tomcat 7 (on centos 5, 64 bit,
12 GB RAM) was crashing without anything being logged in catalina.out
In case of JVM crash, there is supposed to be some hs_err_pid.log file but
that was also not getting generated.
Neither were there any OutOfMemory
Interesting and thanks for your response.
We switched back to VM version 1.6.0_07 (64 bit on Slackware) and everything
was fine. For several unrelated reasons, we switched to Tomcat version 6.0.35
and JVM (Oracle) version 1.6.0_16 and all has been fine for a month or so.
The cause remains
The application has been running for 14 days without failing using the Sun
JVM 1.6.0_7 (per Chuck's suggestion... thanks Chuck.) However, we all know
that is just a work around.
To find the casue, my plan is to bring the latest JVM source code down and
build the JVM on the server with
-
From: Caldarale, Charles R chuck.caldar...@unisys.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Tuesday, March 02, 2010 10:10 PM
Subject: RE: Tomcat dies suddenly
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly
Still looking for the exorcist but we now
This is an update.
Tried Sun JVM 1.6.0_16 (I had already tried 1.6.0_17 and 1.6.0_18... Taylan
thought 1.6.0_16 worked properly in his environment.) Failed with the same
indicator as the other tests: brought it up on Sunday, failed about 11:00AM
this morning (the T105 AMD 64 bit Slackware,
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly
Still looking for the exorcist but we now know that an older
version of the Sun JVM doesn't do the trick.
Not necessarily. 6u10 was a major internal upgrade, so it might be interesting
to try 6u7:
http
Sent: Tuesday, February 23, 2010 7:45 PM
Subject: RE: Tomcat dies suddenly
-Original Message-
From: Carl [mailto:c...@etrak-plus.com]
Sent: Tuesday, February 23, 2010 5:09 AM
To: Tomcat Users List
Subject: Re: Tomcat dies suddenly
Just an update.
After 8 1/2 days, on the newly built
From: Carl [mailto:c...@etrak-plus.com]
Subject: RE: Tomcat dies suddenly
(I switched this comment to Carl's original thread, since that's where it
applies.)
the core files on my systems were in several directories
I wonder if the above is a clue to what's going on. I've always seen core
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/23/2010 6:00 PM, Carl wrote:
There was no core dump or hs_* file.
:(
The strace output looks like it was overwritten this morning at
1:00AM, crap, double crap.
Try something like this:
#!/bin/sh
while(1) ; do
strace -o
@tomcat.apache.org
Sent: Wednesday, February 24, 2010 10:00 AM
Subject: RE: Tomcat dies suddenly
From: Carl [mailto:c...@etrak-plus.com]
Subject: RE: Tomcat dies suddenly
(I switched this comment to Carl's original thread, since that's where it
applies.)
the core files on my systems were in several
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/24/2010 12:10 PM, Carl wrote:
The first core that I saw was in $CATALINA_HOME/bin as expected. The
next crash produced one at root. I thought this might have been because
there is a cron process that runs a shell script in the
Just an update.
After 8 1/2 days, on the newly built Slackware machine with the JRE in the
Slackware distribution removed bebore installing the operating system and
using the newest version of the mysql-connector, the system failed in
exactly the same fashion as the previous attempts: ran
Carl wrote:
...
One more event that may or may not be related.
If it is related, then indeed the time for exorcism may be reached.
I have not touched the
original server (C)
(they all say that)
except to roll new war's out (almost nightly...
minor bug fixes.) This morning, it started
On 23/02/2010 13:46, André Warnier wrote:
Carl wrote:
...
One more event that may or may not be related.
If it is related, then indeed the time for exorcism may be reached.
I have not touched the
original server (C)
(they all say that)
except to roll new war's out (almost nightly...
From: Pid [mailto:p...@pidster.com]
Subject: Re: Tomcat dies suddenly
Check the server time hasn't drifted. Sometimes this can happen if the
files have timestamps that are out.
Also check the timestamps on the .war files - they may be in the future,
causing continuous redeployment
a good day.
Carl
- Original Message -
From: Caldarale, Charles R chuck.caldar...@unisys.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Tuesday, February 23, 2010 8:54 AM
Subject: RE: Tomcat dies suddenly
From: Pid [mailto:p...@pidster.com]
Subject: Re: Tomcat dies suddenly
Carl wrote:
This was an 'oh, crap' moment. Andre was correct: I had commented a
shutdown out of the script I used to deploy (each morning at 1:00AM.)
So, apparently, it was just merrily reploying and redeploying, or
something. All better now (with the proper deploy script.)
Oh well..
I was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/23/2010 7:08 AM, Carl wrote:
One more event that may or may not be related. I have not touched the
original server (C) except to roll new war's out (almost nightly...
minor bug fixes.) This morning, it started producing these messages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/23/2010 7:08 AM, Carl wrote:
Just an update.
After 8 1/2 days, on the newly built Slackware machine with the JRE in
the Slackware distribution removed bebore installing the operating
system and using the newest version of the
- Original Message -
From: Christopher Schultz ch...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Tuesday, February 23, 2010 1:13 PM
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/23/2010 7:08 AM, Carl
-Original Message-
From: Carl [mailto:c...@etrak-plus.com]
Sent: Tuesday, February 23, 2010 5:09 AM
To: Tomcat Users List
Subject: Re: Tomcat dies suddenly
Just an update.
After 8 1/2 days, on the newly built Slackware machine with the JRE in
the
Slackware distribution
To: Tomcat Users List users@tomcat.apache.org
Sent: Tuesday, February 16, 2010 4:55 PM
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 2/16/2010 4:41 PM, André Warnier wrote:
So what now ? I leave this list for 3 days to go earn my keep, and when
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/17/2010 8:14 AM, Carl wrote:
A quick refresher. Server A has been rebuilt with eliminating the JRE
before Slackware is installed. The jre from Slackware was allowed to be
installed and was then removed using the package tool. The
Chris,
Yup, that was my plan.
Thanks,
Carl
- Original Message -
From: Christopher Schultz ch...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, February 17, 2010 10:02 AM
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE
So what now ? I leave this list for 3 days to go earn my keep, and when
I come back this silly crash issue is /still/ not resolved ?
Carl,
still on my trip about the SegFaults caused by some native non-kosher
executable module..
You mentioned earlier that you are using SSL on all requests.
On 16/02/2010 21:41, André Warnier wrote:
Appeal to the experts : considering the lenghtily expounded symptoms,
would it be possible that one obscure corner of the SSL code or data is
being used only occasionally, and that such occasional usage could cause
the symptoms here observed ?
Or the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 2/16/2010 4:41 PM, André Warnier wrote:
So what now ? I leave this list for 3 days to go earn my keep, and when
I come back this silly crash issue is /still/ not resolved ?
Well, we've been waiting for you to bring your expertise to bear
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/14/2010 4:34 PM, Carl wrote:
I upgraded to 5.1.11 but can go back to 3.1.12 in about 15 minutes.
Have been running all day on 5.1.11... no burps so far but I haven't
been pushing it. Tomoroow, I will see if I can break it.
Just don't
On 13 February 2010 15:29, Caldarale, Charles R
chuck.caldar...@unisys.comwrote:
Does memtest86+ fire up enough threads to heat up all the cores?
No. It's a pure memory tester, and it's single-threaded so that it always
knows what's adjacent to each bit.
- Peter
Peter,
That's what I thought.
Thanks,
Carl
- Original Message -
From: Peter Crowther peter.crowt...@melandra.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Sunday, February 14, 2010 5:29 AM
Subject: Re: Tomcat dies suddenly
On 13 February 2010 15:29, Caldarale, Charles R
On 13/02/2010 22:23, Carl wrote:
5) not quite sure of this anymore, but it seems to happen also on
different JVMs, which would tend to rule out a problem with a
particular JVM port.
No, I have only used Sun's 64 bit. Started with 1.6.0_17 and am now
using 1.6.0_18.
That is enough of a
: Tomcat dies suddenly
On 13/02/2010 22:23, Carl wrote:
5) not quite sure of this anymore, but it seems to happen also on
different JVMs, which would tend to rule out a problem with a
particular JVM port.
No, I have only used Sun's 64 bit. Started with 1.6.0_17 and am now
using 1.6.0_18
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/13/2010 5:35 PM, Carl wrote:
I am using the mysql-connector/j version 3.1.12. Interesting because
the latest driver is version 5.1.11. Is this worth a shot or is it
likely to just miuddy the waters? We typically have less than 20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/13/2010 4:04 PM, Carl wrote:
I will start the newly rebuilt server with strace tomorrow morning
before anyone comes on. Hopefully, strace will yield some useful
information.
You'll likely have to run your server repeatedly under
...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Sunday, February 14, 2010 4:15 PM
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/13/2010 5:35 PM, Carl wrote:
I am using the mysql-connector/j version 3.1.12. Interesting because
...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Sunday, February 14, 2010 4:19 PM
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/13/2010 4:04 PM, Carl wrote:
I will start the newly rebuilt server with strace tomorrow morning
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 2/12/2010 7:29 PM, André Warnier wrote:
I would just like to mention that in 90% of the cases where I have seen
a Seg Fault, it was due to the attempted execution of a piece of binary
code not meant for the current platform.
(It's been
suggestions, I am
open to them because I know I know very little.
Thanks,
Carl
- Original Message -
From: Christopher Schultz ch...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 13, 2010 9:46 AM
Subject: Re: Tomcat dies suddenly
-BEGIN
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Tomcat dies suddenly
Maybe another run through memtest86+ would be a good idea.
Does memtest86+ fire up enough threads to heat up all the cores?
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL
the jvm
from source (so I can use it with gdb.)
Thanks,
Carl
- Original Message -
From: Caldarale, Charles R chuck.caldar...@unisys.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 13, 2010 10:29 AM
Subject: RE: Tomcat dies suddenly
From: Christopher
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly
building the jvm from source
Just be aware that Sun is rather explicit about the specific versions of the
compilers and libraries used to build the JVM - it can be a major hassle to get
it all set up right.
- Chuck
: Saturday, February 13, 2010 11:49 AM
Subject: Re: Tomcat dies suddenly
Just a quick way to check if a rogue binary hasn't crept into some
libraries directory :
find . -type f -print -exec file {} \; | more
That should give the same file type most of the time, except the rogue
module
Carl ,
At this point it is probably would be much simpler for you to just move away
from Slackware .
Building jvm from source ,debugging with strace - this is a very hard path .
And once you find the bug - there is nothing that you can do with it.
You are not going to fix jvm/libc bugs ,right?
You
Message -
From: Tsirkin Evgeny tsir...@gmail.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 13, 2010 1:24 PM
Subject: Re: Tomcat dies suddenly
Carl ,
At this point it is probably would be much simpler for you to just move
away
from Slackware .
Building jvm from
like a
memory problem.
Thanks,
Carl
- Original Message -
From: Christopher Schultz ch...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 5:28 PM
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- Original Message -
From: Christopher Schultz ch...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 5:27 PM
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/12/2010 4:59 PM, Carl wrote
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 5:26 PM
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/12/2010 4:44 PM, Carl wrote:
Now, this is embarrassing: I just checked the other server and it also
has a core file
:00 PM
Subject: Re: Tomcat dies suddenly
Carl -
I did have something like this happen to me - not with Tomcat but with
another JEE container. The container would run for a while, without
incident, then suddenly simply die, with nothing in any log, and not on any
apparent time schedule.
We had
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly
We use jdbc with the commons pooling process.
Is your JDBC driver type 4, or does it utilize some native code?
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus
Carl wrote:
Chris,
I find it hard to believe two brand new machines with different
processors, etc. would have a hardware problem that showed itself in
exactly the same way. Further, I have run memTest86 for 30 hours on one
of the servers and it showed nothing (although, as Chuck pointed
@tomcat.apache.org
Sent: Friday, February 12, 2010 3:01 PM
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/12/2010 2:42 PM, Carl wrote:
Great ideas (did you see Chris's response with a way of testing the exit
code?)
[snip]
There is no native code
-sa.com
Sent: Saturday, February 13, 2010 1:56 PM
To: Tomcat Users List users@tomcat.apache.org
Subject: Re: Tomcat dies suddenly
Carl wrote:
Chris,
I find it hard to believe two brand new machines with different
processors, etc. would have a hardware problem that showed itself in
exactly
Andre,
You have the ability to boil things down to the bare essentials.
1) you never saw this issue under a previous JVM 1.5 and Tomcat version
5.5.x
Correct. (Running on a P4 with 32 bit Slackware.)
2) the problem happens on two separate servers, which seems to rule out a
common server
To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 13, 2010 4:08 PM
Subject: RE: Tomcat dies suddenly
If #1 is correct maybe you should just revert back until you can do more
testing outside production.
Of course that's only if you're not using some tomcat 6/java 1.6 specific
, Charles R chuck.caldar...@unisys.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 13, 2010 3:51 PM
Subject: RE: Tomcat dies suddenly
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly
We use jdbc with the commons pooling process.
Is your JDBC
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly
This Tomcat is straight out of the box except for some modifications
to JAVA_OPTS in tomcat/bin/catalina.sh
Have you tried using the default GC mechanism, rather than CMS? (Sorry if I'm
repeating something you've
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly
I am using the mysql-connector/j version 3.1.12. Interesting
because the latest driver is version 5.1.11. Is this worth a
shot or is it likely to just miuddy the waters?
I think it would be muddying, since I'm
-
From: Caldarale, Charles R chuck.caldar...@unisys.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 13, 2010 5:39 PM
Subject: RE: Tomcat dies suddenly
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly
This Tomcat is straight out of the box
This problem continues to plague me.
A quick recap so you don't have to search your memory or archives.
The 10,000 foot view: new Dell T105 and T110, Slackware 13.0 (64 bit),
latest Java (64 bit) and latest Tomcat. Machines only run Tomcat and a
small, special purpose Java server (which I
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly
The fact that the failures occur after some amount of processing
implies that the issue is related to memory usage, and, potentially,
caused by a memory leak in the application.
Actually, it's looking less and less
: Friday, February 12, 2010 8:39 AM
Subject: RE: Tomcat dies suddenly
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly
The fact that the failures occur after some amount of processing
implies that the issue is related to memory usage, and, potentially,
caused by a memory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/12/2010 7:20 AM, Carl wrote:
The 10,000 foot view: new Dell T105 and T110, Slackware 13.0 (64 bit),
latest Java (64 bit) and latest Tomcat. Machines only run Tomcat and a
small, special purpose Java server (which I have also moved to
I've been following this thread with interest, but haven't weighed in since I'm
doing much development these days. I have to say that I'm agreeing with Chuck
and Chris that it is a resource issue - especially since it doesn't appear to
be a problem unless under load. Also, the OOP mentioned
You haven't said if you tried a previous java version or tomcat version
(6.0.20)?
-Tony
Sent from my Windows® phone.
-Original Message-
From: Carl c...@etrak-plus.com
Sent: Friday, February 12, 2010 5:22 AM
To: Tomcat Users List users@tomcat.apache.org
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 2/12/2010 10:31 AM, Jeffrey Janner wrote:
Also, the OP mentioned that it doesn't seem to occur if only the
production app is being hit. It takes someone using one of the other
copies first to generate the problem. So the questions
, February 12, 2010 10:13 AM
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/12/2010 7:20 AM, Carl wrote:
The 10,000 foot view: new Dell T105 and T110, Slackware 13.0 (64 bit),
latest Java (64 bit) and latest Tomcat. Machines only run Tomcat
List users@tomcat.apache.org
Sent: Friday, February 12, 2010 10:31 AM
Subject: RE: Tomcat dies suddenly
I've been following this thread with interest, but haven't weighed in
since I'm doing much development these days. I have to say that I'm
agreeing with Chuck and Chris that it is a resource
On 12 February 2010 16:43, Carl c...@etrak-plus.com wrote:
1. There is no place in the code that we intentionally put an exit(). I
have grepped for exit() and found nothing. The system stops in a different
place every time... the last entry in catalina.out has never been the same
(over
Is it possible to run this server with a basic tomcat application under load
to rule out the application causing the crash?
On Fri, Feb 12, 2010 at 4:20 AM, Carl c...@etrak-plus.com wrote:
This problem continues to plague me.
A quick recap so you don't have to search your memory or archives.
2010/2/12 Carl c...@etrak-plus.com:
More details: the Dell 105 has an AMD processor and (currently) 8 GB memory.
The T110 has a Xeon 3440 processor and 4 GB memory. The current Java
version is 1.6.0_18-b07. The current Tomcat version is 6.0.24.
Actually, 6.0.24 version *will* exit silently
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Subject: Re: Tomcat dies suddenly
Actually, 6.0.24 version *will* exit silently if it is terminated
by a signal.
To reproduce (on Windows):
1. Run Tomcat in a console window.
2. Press Ctrl+C
3. Tomcat shutdowns in several
.)
Thanks,
Carl
- Original Message -
From: Anthony J. Biacco abia...@formatdynamics.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 10:36 AM
Subject: RE: Tomcat dies suddenly
You haven't said if you tried a previous java version or tomcat version
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 2/12/2010 10:31 AM, Jeffrey Janner wrote:
Also, the OP mentioned that it doesn't seem to occur if only the
production app is being hit. It takes someone using one of the other
copies first to generate
and I am familiar with mayhem of buffer overruns, pointer screwups, etc.)
Thanks,
Carl
- Original Message -
From: Peter Crowther peter.crowt...@melandra.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 12:05 PM
Subject: Re: Tomcat dies suddenly
On 12
: Friday, February 12, 2010 12:07 PM
Subject: Re: Tomcat dies suddenly
Is it possible to run this server with a basic tomcat application under
load
to rule out the application causing the crash?
On Fri, Feb 12, 2010 at 4:20 AM, Carl c...@etrak-plus.com wrote:
This problem continues to plague
Carl wrote:
.. a lot of messages, and I have not yet read all of them, but I
sympathise with the predicament.
I am very far from any kind of Java expertise, so just something that I
vaguely seem to remember, although it may be from a very long time ago,
not applicable, already mentioned by
users@tomcat.apache.org
Sent: Friday, February 12, 2010 1:17 PM
Subject: Re: Tomcat dies suddenly
2010/2/12 Carl c...@etrak-plus.com:
More details: the Dell 105 has an AMD processor and (currently) 8 GB
memory.
The T110 has a Xeon 3440 processor and 4 GB memory. The current Java
version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/12/2010 2:42 PM, Carl wrote:
Great ideas (did you see Chris's response with a way of testing the exit
code?)
[snip]
There is no native code in the application (used to do a lot of work in
C and I am familiar with mayhem of buffer
insights.
Carl
- Original Message -
From: Caldarale, Charles R chuck.caldar...@unisys.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 1:57 PM
Subject: RE: Tomcat dies suddenly
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Subject: Re: Tomcat
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly
Just tried kill -9 xxx (the process id of the java process) on
one the servers not currently in production and it put nothing
in the catalina.out file and nothing in the Slackware messages
file.
The message won't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/12/2010 3:03 PM, Carl wrote:
Oooo, that's interesting. Just tried kill -9 xxx (the process id of the
java process) on one the servers not currently in production and it put
nothing in the catalina.out file and nothing in the Slackware
from Chris and Peter.
Thanks for your insights.
Carl
- Original Message - From: Caldarale, Charles R
chuck.caldar...@unisys.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 1:57 PM
Subject: RE: Tomcat dies suddenly
From: Konstantin Kolinko
, 2010 2:49 PM
Subject: Re: Tomcat dies suddenly
Carl wrote:
.. a lot of messages, and I have not yet read all of them, but I
sympathise with the predicament.
I am very far from any kind of Java expertise, so just something that I
vaguely seem to remember, although it may be from a very long
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/12/2010 2:42 PM, Carl wrote:
Great ideas (did you see Chris's response with a way of testing the exit
code?)
[snip]
There is no native code in the application (used to do a lot of work in
C and I am
.
Thank you for the help.
Carl
- Original Message -
From: Caldarale, Charles R chuck.caldar...@unisys.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 3:09 PM
Subject: RE: Tomcat dies suddenly
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies
Carl wrote:
Andre,
Thanks for the response.
I have read almost all of your posts and realy enjoy the way to take
problems apart.
Keep on thinking.
I'm not quite sure how to take the above answer..
So, just in case, and maybe to my own ultimate embarassment, I want to
indicate that I was
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 3:10 PM
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/12/2010 3:03 PM, Carl wrote:
Oooo, that's interesting. Just tried kill -9 xxx (the process id of the
java process) on one
to test the ideas from Chris and Peter.
Thanks for your insights.
Carl
- Original Message - From: Caldarale, Charles R
chuck.caldar...@unisys.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 1:57 PM
Subject: RE: Tomcat dies suddenly
From: Konstantin Kolinko
around to see if I could
find it myself.
Thanks,
Carl
- Original Message -
From: André Warnier a...@ice-sa.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 3:34 PM
Subject: Re: Tomcat dies suddenly
Carl wrote:
Andre,
Thanks for the response.
I
Carl wrote:
Andre,
Take my comment as a compliment because that is the way it was meant...
you have helped a lot of people on this least and I, for one, really
appreciate that.
I was waiting to see if someone could give me an idea how to implement
what you remembered and, if not, then I
Subject: Re: Tomcat dies suddenly
Carl wrote:
Andre,
Thanks for the response.
I have read almost all of your posts and realy enjoy the way to take
problems apart.
Keep on thinking.
I'm not quite sure how to take the above answer..
So, just in case, and maybe to my own ultimate
Donn Aiken wrote:
...
For each
leaked connection, we had an open file descriptor that never went away,
until the process went away. If memory serves, we finally found it by
looking at entries in /proc/{pid of jvm}/fd, doing a bunch of find . | wc
and watching that over time.
As another
.
Thanks,
Carl
- Original Message -
From: Christopher Schultz ch...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 3:01 PM
Subject: Re: Tomcat dies suddenly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/12/2010 2:42 PM
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
... 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
, 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
it is unlikely to be the
culprit.
Thanks,
Carl
- Original Message -
From: Konstantin Kolinko knst.koli...@gmail.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 5:08 PM
Subject: Re: Tomcat dies suddenly
Can it be hardware? Do you have ways to monitor temperature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/12/2010 4:44 PM, Carl wrote:
Now, this is embarrassing: I just checked the other server and it also
has a core file with the date and time of the last failure in the
tomcat/bin directory. And, it shows a seg fault at exactly the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl,
On 2/12/2010 4:59 PM, Carl wrote:
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.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 2/12/2010 3:34 PM, André Warnier wrote:
Carl wrote:
Andre,
Thanks for the response.
I have read almost all of your posts and realy enjoy the way to take
problems apart.
Keep on thinking.
I'm not quite sure how to take the above
1 - 100 of 185 matches
Mail list logo
