Tsirkin,
I tried part of that.
I brought up a server with openSuse (64 bit), the latest Sun Java and the
latest Tomcat. Failed in about 15 minutes with the same indicators (no
tracks in any log, didn't know to look for a core file at that time.) Could
try this again and check for the core file to see if the failure is the
same.
I agree building from source and debugging is a very hard road. Have been
trying to find a solution for almost three months and everything I have
tried has failed.
There appear to be only two moving parts: the operating system and the jvm
(we now know the failure is when the jvm seg faults.) Maybe I should try a
different jvm but I have always believed Sun's was most likely the most
stable and bug free.
Another option is to create a separate Tomcat for each application. This
would require reworking and rethinking the applications with no guarantee of
success anyway.
It would seem that there is something wrong in my setup because I can't
believe every 64 bit Slackware/Tomcat has failed as we would likely see that
on this list.
I am certainly open to any suggestion and I appreciate your thoughts.
Thanks,
Carl
----- Original 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 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 could report it and wait for new release .
Probably your best bet would be use another distro and download Sun's jvm
from thier site.
Evgeny
So, the only way to get the details would seem to be to build the jvm
from
source (I have downloaded the source but haven't built the jvm yet.) I
don't know how to force a java stack dump at point of failure, not even
certain it is possible because it would seem the the failure in the C
code
in the jvm would mean the jvm would stop before it could give a stack
trace.
Understand that this is my best guess and that this area is removed from
my
usual mundane Java application development. If anyone has suggestions, I
am
open to them because I know I know very little.
Thanks,
Carl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
