[ajug-members] Java crash with Tomcat

[Sony Antony]

SIGSEGV can only happen from native code and almost certainly as a
result of a dangling pointer. ( and not from other external processes
)
you can print the stacktrace from the resulting core using gdb, to see
which subsystem generated the core.
--sony

On 6/23/08, Chris Fowler <cfowler at outpostsentinel.com> wrote:
> 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
>