[ajug-members] Java crash with Tomcat
Thomas, Dave
dthomas at tandbergtv.com
Mon Jun 23 14:09:20 EDT 2008
You shouldn't need to recompile Tomcat, simply use a binary release,
latest 4.1.37. If possible, use a newer Tomcat, such as 6.0. Check
what else the server is running (such as a cron job). If all else
fails, test & replace the RAM.
-----Original Message-----
From: Chris Fowler [mailto:cfowler at outpostsentinel.com]
Sent: Monday, June 23, 2008 10:57 AM
To: ajug-members at ajug.org
Subject: [ajug-members] Java crash with Tomcat
I'm running into an interesting problem with Tomcat 4.1.30 on CentOS 5.1
running Java 6.06. Each morning around
10am I get a SIGSEGV crash.
Here is the crash report:
http://support.opsdc.com/~support/crash.txt
I've looked at the apache logs and this software has very little traffic
and usually around 10am no one is using it.
The only thing accessing the main page is a monitor that makes sure it
is still running by looking for a login page.
I'm not quite sure what might be causing it.
Software on server:
OS: CentOS 5.1
App Server: Tomcat 4.1.30
Java: 6.06
Apache: 2.0.55
Now I am running Tomcat as copied from a Fedora Core 2. I've been
thinking I may need to recompile 4.1.30 from source using Jdk6.
Originally
I had this running on FC2,JDK1.4,Tomcat 4.1.30. I decided to upgrade to
CentOS based on the extended support period.
Chris
_______________________________________________
ajug-members mailing list
ajug-members at ajug.org
http://www.ajug.org/mailman/listinfo/ajug-members
**********************************************************************
This email, its content and any attachments is PRIVATE AND
CONFIDENTIAL to TANDBERG Television, Part of the Ericsson Group.
If received in error please notify the sender and destroy the original
message and attachments.
www.tandbergtv.com
**********************************************************************
More information about the ajug-members
mailing list