You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Rogerio Pazini <ro...@gmail.com> on 2007/05/09 13:41:36 UTC
Kernel Panic - Tomcat Shutdown
Hi,
I´m just trying to configure a new server with RHEL 4.0 installed together
with JDK 1.6.0 and Apache Tomcat/5.5.17 installed. We have no problem to
start it up (Tomcat) but when it try to shut it down, I have many kernel
panic messages and the machine got frozen. Does anybody had similar problem
before ? If positive what could be happening ?
Tks in advance !
Rogério
Re: Kernel Panic - Tomcat Shutdown
Posted by Leon Rosenberg <ro...@googlemail.com>.
On 5/9/07, Rogerio Pazini <ro...@gmail.com> wrote:
>
> Does anyone know if there´s any incompatibility of this JDK version with
> RHEL 4.0 ?
>
I think this is the false place to ask :-)
regards
Leon
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Kernel Panic - Tomcat Shutdown
Posted by Rogerio Pazini <ro...@gmail.com>.
David, tks 4 your email ...
I didn´t try to follow what you suggested me yet regarding the hw (mem +
netwk). Instead of that, I uninstalled JDK version 1.6.0_01 and installed
1.5.0_11 one. After that, I got no kernel panic messages to start or
shutdown Tomcat.
Does anyone know if there´s any incompatibility of this JDK version with
RHEL 4.0 ?
Tks again.
Rogério.
2007/5/9, David Delbecq <de...@oma.be>:
>
> Kernel Panic happens due to bug at the kernel level. Normally, even
> deeply broken applications should not generate a kernel panic.
> Possible causes:
> 1) Broken network module, which generates an error during unbinding of
> tomcat from interface. Unless your interface model is very recent and
> kernel module associated with it is indicated 'experimental', should not
> happen
> 2) Broken hardware. A broken network interface could generate unexpected
> irq, return values in unexpected range to driver, which could then crash
> if such condition was not expected. Also, i'll recommend to check the
> most common cause of kernel or random application crash : memory. Run a
> memtest86 for a few hours to ensure memory is not broken.
>
> My bet is on network interface, if this happens systematically. Try
> unloading network interfaces then start/stop tomcat, it will only attach
> to localhost, where no network hardware is involved.
> En l'instant précis du 09/05/07 13:41, Rogerio Pazini s'exprimait en ces
> termes:
> > Hi,
> >
> > I´m just trying to configure a new server with RHEL 4.0 installed
> > together
> > with JDK 1.6.0 and Apache Tomcat/5.5.17 installed. We have no problem to
> > start it up (Tomcat) but when it try to shut it down, I have many kernel
> > panic messages and the machine got frozen. Does anybody had similar
> > problem
> > before ? If positive what could be happening ?
> >
> > Tks in advance !
> >
> > Rogério
> >
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: Kernel Panic - Tomcat Shutdown
Posted by David Delbecq <de...@oma.be>.
Kernel Panic happens due to bug at the kernel level. Normally, even
deeply broken applications should not generate a kernel panic.
Possible causes:
1) Broken network module, which generates an error during unbinding of
tomcat from interface. Unless your interface model is very recent and
kernel module associated with it is indicated 'experimental', should not
happen
2) Broken hardware. A broken network interface could generate unexpected
irq, return values in unexpected range to driver, which could then crash
if such condition was not expected. Also, i'll recommend to check the
most common cause of kernel or random application crash : memory. Run a
memtest86 for a few hours to ensure memory is not broken.
My bet is on network interface, if this happens systematically. Try
unloading network interfaces then start/stop tomcat, it will only attach
to localhost, where no network hardware is involved.
En l'instant précis du 09/05/07 13:41, Rogerio Pazini s'exprimait en ces
termes:
> Hi,
>
> I´m just trying to configure a new server with RHEL 4.0 installed
> together
> with JDK 1.6.0 and Apache Tomcat/5.5.17 installed. We have no problem to
> start it up (Tomcat) but when it try to shut it down, I have many kernel
> panic messages and the machine got frozen. Does anybody had similar
> problem
> before ? If positive what could be happening ?
>
> Tks in advance !
>
> Rogério
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org